Triple
T37264136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aurora |
E924334
|
entity |
| Predicate | isAcross |
P94992
|
FINISHED |
| Object | Mississippi River from main part of New Orleans |
—
|
LITERAL 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: Mississippi River from main part of New Orleans | Statement: [Aurora, isAcross, Mississippi River from main part of New Orleans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAcross Context triple: [Aurora, isAcross, Mississippi River from main part of New Orleans]
-
A.
isCrossBetween
Indicates that one entity is a hybrid or intermediate form resulting from the combination or mixing of two other entities.
-
B.
across
chosen
Indicates a spatial relationship where one entity is on the opposite side of, or extending from one side to the other side of, another entity or area.
-
C.
hasCross
Indicates that one entity possesses, displays, or is marked by a cross in relation to another entity or context.
-
D.
crossingOf
Indicates that one entity serves as the intersection or crossing point of two or more linear features, such as roads, paths, or tracks.
-
E.
crossedBy
Indicates that one entity (typically a path, line, or boundary) is intersected or traversed by another entity.
- F. None of above.
Provenance (3 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_69f76eabd6c481909d414a80a1345c98 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb4134225081909fd60703b8cae397 |
completed | May 6, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69fb35bf767081908de8345358ca7f44 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:15 p.m.