Triple
T9033409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yellow Hook |
E216429
|
entity |
| Predicate | nameChangeOccurredIn |
P39961
|
FINISHED |
| Object | 19th century |
—
|
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: 19th century | Statement: [Yellow Hook, nameChangeOccurredIn, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameChangeOccurredIn Context triple: [Yellow Hook, nameChangeOccurredIn, 19th century]
-
A.
changedNameIn
chosen
Indicates that an entity has altered or adopted a different name within a specific context, time period, or jurisdiction.
-
B.
changedNameOn
Indicates that an entity altered or updated its name at a specific point in time or on a particular date.
-
C.
nameChangeEvent
Indicates an event in which an entity’s name is changed from one value to another.
-
D.
nameChangeDescribedIn
Indicates that a change of name for an entity is documented or specified within a particular source or description.
-
E.
changedNameInHonorOf
Indicates that an entity altered its name specifically to honor or pay tribute to 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_69ca83d10b608190b2b2f8e0a7faaf14 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc6aa248bc8190a55cfc2a5306ab20 |
completed | April 1, 2026, 12:45 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee3597c81908919cf866ae95c24 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:08 p.m.