Triple
T29591145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Francis River |
E754162
|
entity |
| Predicate | lendsNameTo |
P39771
|
FINISHED |
| Object | St. Francois Mountains |
—
|
NE NERFINISHED |
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: St. Francois Mountains | Statement: [St. Francis River, lendsNameTo, St. Francois Mountains]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lendsNameTo Context triple: [St. Francis River, lendsNameTo, St. Francois Mountains]
-
A.
namedAs
chosen
Indicates that one entity is given, known by, or referred to using the name of another entity.
-
B.
importName
Indicates that one entity brings another entity into a scope, module, or context under a specific name used for reference.
-
C.
hasNameGivenTo
Indicates that one entity is the name that has been assigned or given to another entity.
-
D.
namedTo
Indicates that one entity has been given or assigned a specific name referring to another entity.
-
E.
usesNameDueTo
Indicates that one entity adopts or applies a particular name for another entity specifically because of some motivating reason, circumstance, or dependency.
- 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_69f0ef836ac88190bd809dc58b5ec907 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f66db3419081908757734f62faf927 |
completed | May 2, 2026, 9:33 p.m. |
| PD | Predicate disambiguation | batch_69f6659d36208190b01412600a4ed57d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 6:14 p.m.