Triple
T30533771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harlansburg, Indiana |
E777082
|
entity |
| Predicate | isInNorthAmericanCountry |
P58254
|
FINISHED |
| Object | United States of America |
E14
|
NE FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: United States of America | Statement: [Harlansburg, Indiana, isInNorthAmericanCountry, United States of America]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInNorthAmericanCountry Context triple: [Harlansburg, Indiana, isInNorthAmericanCountry, United States of America]
-
A.
isNorthAmericanTimeZone
Indicates that a given time zone is located within the North American region.
-
B.
isInUnitedStates
chosen
Indicates that one entity is located within the geographic or political boundaries of the United States.
-
C.
isInContinent
Indicates that one place or region is geographically located within the boundaries of a specific continent.
-
D.
isInNortheasternUS
Indicates that a location or entity is situated within the northeastern region of the United States.
-
E.
locatedInUSRegion
Indicates that one entity is geographically situated within a specified region of the United States.
- F. None of above.
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f2249c11508190ae7e955755ccfb01 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68a16debc8190a12f5f65ced055d7 |
completed | May 2, 2026, 11:34 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a28c7b225e0819087bd6dab22c04874 |
completed | June 10, 2026, 2:10 a.m. |
| PD | Predicate disambiguation | batch_69f6860def1c81909d79e1f088c4b5e5 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:18 p.m.