Triple
T34059643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | C. F. Smith |
E873455
|
entity |
| Predicate | hasFortNamedAfter |
P107513
|
FINISHED |
| Object | Fort C. F. Smith |
—
|
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: Fort C. F. Smith | Statement: [C. F. Smith, hasFortNamedAfter, Fort C. F. Smith]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFortNamedAfter Context triple: [C. F. Smith, hasFortNamedAfter, Fort C. F. Smith]
-
A.
hasCharacterNamedAfter
Indicates that one entity has a character whose name is derived from or intentionally based on another entity.
-
B.
hasPrincipleNamedAfter
Indicates that an entity has a principle, rule, or law that is named after a specified entity.
-
C.
hasNamedAfterPerson
chosen
Indicates that one entity is named in honor of, or derived from the name of, a specific person.
-
D.
hasOpeningNamedAfter
Indicates that an opening (such as in a game, work, or structure) is named after a particular entity.
-
E.
hasNamesakeFeature
Indicates that one entity has a feature (such as a place, object, or structure) that is named after 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_69f349a4af208190afa14888f9c9fb9d |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fdd2be648c8190b60b3d1caeb44364 |
completed | May 8, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_69fdd14a5c708190a6f95ec61f4fc28f |
completed | May 8, 2026, 12:04 p.m. |
Created at: May 1, 2026, 1:52 a.m.