Triple
T1524621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dan David Prize |
E32306
|
entity |
| Predicate | formerStructure |
P16344
|
FINISHED |
| Object | three time-dimension categories |
—
|
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: three time-dimension categories | Statement: [Dan David Prize, formerStructure, three time-dimension categories]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerStructure Context triple: [Dan David Prize, formerStructure, three time-dimension categories]
-
A.
previousStructure
Indicates that one structure directly precedes another in a defined sequence or configuration.
-
B.
formerType
chosen
Indicates that one entity previously had a certain type, role, or classification but no longer does.
-
C.
encodingStructure
Indicates the structural scheme or format used to encode information or data.
-
D.
currentStructure
Indicates that an entity is the present or active structural configuration or organization associated with another entity.
-
E.
viaStructure
Indicates that one entity is connected to or accessed through a particular structural element or medium.
- 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_69a885e9b0ac819093a9806ad0efc82c |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a93d4756888190bf3872154de11539 |
completed | March 5, 2026, 8:22 a.m. |
| PD | Predicate disambiguation | batch_69a907ac7ea081908dd95bb5cc3b9847 |
completed | March 5, 2026, 4:33 a.m. |
Created at: March 4, 2026, 7:26 p.m.