Triple
T9313031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | D-root |
E224049
|
entity |
| Predicate | identifiedByLetter |
P5539
|
FINISHED |
| Object | D |
—
|
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: D | Statement: [D-root, identifiedByLetter, D]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: identifiedByLetter Context triple: [D-root, identifiedByLetter, D]
-
A.
letterOrNumberDesignation
Indicates that something is identified or labeled using a specific letter, number, or combination of both.
-
B.
hasLetterBy
Indicates that an entity possesses or is associated with a letter authored or sent by another entity.
-
C.
identifierFor
Indicates that one entity serves as a unique identifying label or code for another entity.
-
D.
hasLetterDesignation
chosen
Indicates that an entity is assigned or associated with a specific letter-based designation or code.
-
E.
usesAdditionalLettersFrom
Indicates that one entity forms or derives its representation by incorporating extra letters taken from another entity beyond those originally present.
- 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_69ca8425f4fc81909c1c586e9a5b7530 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd20b048a081909fd7ec0b6b863063 |
completed | April 1, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69cc7a61e9a4819096eb014f3791ef2e |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:37 p.m.