Triple
T22695164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ND280 |
E561154
|
entity |
| Predicate | tookFirstData |
P73905
|
FINISHED |
| Object | around 2009 |
—
|
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: around 2009 | Statement: [ND280, tookFirstData, around 2009]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tookFirstData Context triple: [ND280, tookFirstData, around 2009]
-
A.
firstTakenAt
chosen
Indicates the time or date at which something was initially taken, captured, or recorded for the first time.
-
B.
takenAs
Indicates that one entity is regarded, used, or accepted in the role, capacity, or form of another entity.
-
C.
tookHeadOf
Indicates that one entity removed or claimed the head (literal or symbolic) of another entity.
-
D.
initialDataGivenOn
Indicates that some initial or starting data was provided or made available at a specific time or on a particular date.
-
E.
takenInBy
Indicates that one entity is absorbed, ingested, or otherwise brought inside and contained by another entity.
- 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_69e2454e615481909c177440be559d2c |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1789d46c881908176bc8e26f366f6 |
completed | April 29, 2026, 3:18 a.m. |
| PD | Predicate disambiguation | batch_69ee62b2259c819091ed1387a748b9f3 |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:14 p.m.