Triple
T23567522
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 634-5789 (Soulsville, U.S.A.) |
E579410
|
entity |
| Predicate | hasNumericTitleElement |
P103300
|
FINISHED |
| Object | 634-5789 |
—
|
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: 634-5789 | Statement: [634-5789 (Soulsville, U.S.A.), hasNumericTitleElement, 634-5789]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumericTitleElement Context triple: [634-5789 (Soulsville, U.S.A.), hasNumericTitleElement, 634-5789]
-
A.
hasTitleType
Indicates that an entity holds a specific kind or category of title (such as job title, honorific, or formal designation).
-
B.
hasTitularyElement
Indicates that an entity includes or is associated with a specific titulary component, such as a formal title, epithet, or honorific element, as part of its designation.
-
C.
hasSymbolicTitle
Indicates that an entity holds a title or designation that is primarily symbolic or honorary rather than functional or operational.
-
D.
isTitled
Indicates that an entity holds or is assigned a specific formal title or designation.
-
E.
hasTitleFeature
chosen
Indicates that an entity possesses a specific characteristic, attribute, or element related to its title.
- 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_69e245fe24588190888f3aec8407d8e3 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1af6e11008190bdd28c3f85e3004e |
completed | April 29, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69f118bcc0b08190b25a8dddfd461a0e |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:35 p.m.