Triple
T13938461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crescent City |
E335178
|
entity |
| Predicate | namedForFeature |
P111871
|
FINISHED |
| Object | distinctive bend of the Ohio River |
—
|
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: distinctive bend of the Ohio River | Statement: [Crescent City, namedForFeature, distinctive bend of the Ohio River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namedForFeature Context triple: [Crescent City, namedForFeature, distinctive bend of the Ohio River]
-
A.
namedFeature
Indicates that an entity has a specific feature or attribute that is explicitly given a name.
-
B.
namedForFamily
Indicates that one entity is named in honor of, or derived from the name of, a particular family or family group.
-
C.
namedForField
Indicates that one entity is named after, or in honor of, a particular field, discipline, or area of study.
-
D.
namedAs
Indicates that one entity is given, known by, or referred to using the name of another entity.
-
E.
namedIn
Indicates that one entity is explicitly mentioned or referenced by name within another entity (such as a document, statement, or record).
- F. None of above. chosen
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_69d81c6081b88190b53e317c3370c8fe |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2cf5cc8c8190bea74291702b2925 |
completed | April 14, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69dbc873052c8190b33ff7f7c5a4e7ee |
completed | April 12, 2026, 4:29 p.m. |
| PDg | Predicate description generation | batch_69dcad0fc42c8190ada203febd57e851 |
completed | April 13, 2026, 8:45 a.m. |
Created at: April 9, 2026, 10:17 p.m.