Triple
T6034077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AMBER |
E134374
|
entity |
| Predicate | dataTakingStartPlanned |
P12530
|
FINISHED |
| Object | 2020s |
—
|
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: 2020s | Statement: [AMBER, dataTakingStartPlanned, 2020s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataTakingStartPlanned Context triple: [AMBER, dataTakingStartPlanned, 2020s]
-
A.
plannedAt
Indicates that an event, action, or activity is scheduled or intended to occur at a specific time or date.
-
B.
planningStarted
Indicates that the process of planning for a particular task, project, or event has been initiated.
-
C.
dataTakingPeriodNumber
Indicates the specific sequential period or interval during which data is collected or recorded.
-
D.
startsAt
chosen
Indicates that an event, process, or state begins at a specific time, location, or point in a sequence.
-
E.
plannedTarget
Indicates that one entity has been designated or selected as the intended target or objective of another entity’s planned action or operation.
- 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_69c0087515148190a97475d412563865 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c056b220608190b156be95632cf3b3 |
completed | March 22, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69c049e9a68c81909da0cfe4779ce9b5 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:08 p.m.