Triple
T27655261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Destiny |
E696974
|
entity |
| Predicate | attachedToSince |
P10139
|
FINISHED |
| Object | 2001-02 |
—
|
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: 2001-02 | Statement: [Destiny, attachedToSince, 2001-02]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attachedToSince Context triple: [Destiny, attachedToSince, 2001-02]
-
A.
permanentlyAttachedSince
Indicates that one entity has been fixed or joined to another in a way intended to be lasting, starting from a specific point in time.
-
B.
attachedTo
chosen
Indicates that one entity is physically or logically fastened, connected, or joined to another entity.
-
C.
basedAtSince
Indicates that an entity has been continuously based or located at a specific place starting from a given point in time.
-
D.
appliedSince
Indicates that a particular condition, rule, status, or action has been in effect starting from a specified point in time and continues from that date onward.
-
E.
representedSince
Indicates that one entity has been acting as a representative or agent for another entity continuously from a specified starting time.
- 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_69ef590abd3c8190834d0193bde12007 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f631d8bb9881908a1b01a501d96cfc |
completed | May 2, 2026, 5:18 p.m. |
| PD | Predicate disambiguation | batch_69f62c1a92648190835a2c5250d8c758 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 2:34 p.m.