Triple
T23395167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DDO |
E559336
|
entity |
| Predicate | hasEntryExample |
P152088
|
FINISHED |
| Object | DDO 50 |
—
|
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: DDO 50 | Statement: [DDO, hasEntryExample, DDO 50]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEntryExample Context triple: [DDO, hasEntryExample, DDO 50]
-
A.
hasEntryOn
Indicates that one entity contains or includes an entry, record, or listing about another entity.
-
B.
hasEntryType
Indicates that something is associated with a specific category or type of entry within a system or dataset.
-
C.
hasEntryFormula
Indicates that something is associated with a specific formula used to represent its entry or defining expression.
-
D.
hasShallowEntry
Indicates that an entity provides or features an entry or access point that is shallow in depth or incline.
-
E.
hasTimedEntry
Indicates that an entity is associated with an entry or access that is constrained or defined by a specific time or time period.
- F. None of above. chosen
Provenance (4 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_69e24549610c8190a069d6411ce5f661 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1a4db1c888190ace5d58bcc8645c1 |
completed | April 29, 2026, 6:27 a.m. |
| PD | Predicate disambiguation | batch_69f061dde2e481908308952f9c0d3c2e |
completed | April 28, 2026, 7:29 a.m. |
| PDg | Predicate description generation | batch_69f07cbbd7488190ab3c8ae7d0fb68bf |
completed | April 28, 2026, 9:24 a.m. |
Created at: April 17, 2026, 5:36 p.m.