Triple
T34749323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ALCA |
E1001723
|
entity |
| Predicate | deadlineOriginallyEnvisaged |
P8546
|
FINISHED |
| Object | 2005 |
—
|
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: 2005 | Statement: [ALCA, deadlineOriginallyEnvisaged, 2005]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deadlineOriginallyEnvisaged Context triple: [ALCA, deadlineOriginallyEnvisaged, 2005]
-
A.
scheduledToEnd
Indicates that an event, process, or state is planned or expected to conclude at a specified time or under specified conditions.
-
B.
airedUntil
Indicates the date or time up to which something, typically a broadcast or series, was shown or transmitted.
-
C.
originallyPlannedFor
Indicates that something was initially intended, designed, or scheduled to be used for or associated with a particular purpose, event, or entity, regardless of what ultimately occurred.
-
D.
endedDueTo
Indicates that an event, process, or state came to a conclusion specifically because of a particular cause or condition.
-
E.
hasDeadline
chosen
Indicates that an entity is associated with a specific due date or time by which it must be completed or fulfilled.
- 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_69f76db0367081909b57c50a7fb03025 |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f77ffa6b68819090257fed3802c239 |
completed | May 3, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69f7795978c481909e152cd1bd02dd07 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 3, 2026, 3:59 p.m.