Triple
T23321760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kinchafoonee Creek |
E591169
|
entity |
| Predicate | hasNotable |
P494
|
FINISHED |
| Object | Kinchafoonee Creek bridge crossings |
—
|
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: Kinchafoonee Creek bridge crossings | Statement: [Kinchafoonee Creek, hasNotable, Kinchafoonee Creek bridge crossings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotable Context triple: [Kinchafoonee Creek, hasNotable, Kinchafoonee Creek bridge crossings]
-
A.
isNotable
Indicates that an entity is recognized as significant, prominent, or worthy of attention within a particular context or domain.
-
B.
hasNotableHead
Indicates that an entity is associated with a particularly prominent or distinguished leader or chief figure.
-
C.
hasNotableSubject
chosen
Indicates that an entity is associated with a subject that is particularly significant, prominent, or noteworthy in relation to it.
-
D.
hasNotableReference
Indicates that one entity makes a significant or noteworthy mention of, or allusion to, another entity.
-
E.
hasNotableIssue
Indicates that an entity is associated with a significant problem, concern, or defect that is noteworthy or exceptional compared to typical cases.
- 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_69e25d1effe4819096907f95f610dbff |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1978672148190bb90804361bb896b |
completed | April 29, 2026, 5:30 a.m. |
| PD | Predicate disambiguation | batch_69effcf8ca2c8190887d4f4656617d21 |
completed | April 28, 2026, 12:19 a.m. |
Created at: April 17, 2026, 5:07 p.m.