Triple
T20565506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haji |
E504955
|
entity |
| Predicate | usedInFormalAddress |
P64298
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Haji, usedInFormalAddress, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInFormalAddress Context triple: [Haji, usedInFormalAddress, yes]
-
A.
usedInStyleOfAddress
chosen
Indicates that one entity is used as a form or style of address when referring to or speaking to another entity.
-
B.
usedInFormalTitleOf
Indicates that something is employed as part of the official or formal title of an entity.
-
C.
usedInFormalContexts
Indicates that something is employed or occurs primarily within formal or official situations, settings, or styles of communication.
-
D.
formalSetting
Indicates that the associated interaction, event, or context occurs in a formal or official setting governed by explicit social or institutional norms.
-
E.
honorificUse
Indicates that one entity refers to or addresses another using an honorific title or respectful linguistic form.
- 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_69e0b4b6587c8190aee63dc7cff244ea |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a7a228948190b47a3a61f239e00d |
completed | April 20, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69e59ff0116c8190a163ff28ed01430a |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:39 a.m.