Triple
T31925919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CCTV Headquarters structural concept |
E815107
|
entity |
| Predicate | usedForProjectCompletionYear |
P85809
|
FINISHED |
| Object | 2012 |
—
|
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: 2012 | Statement: [CCTV Headquarters structural concept, usedForProjectCompletionYear, 2012]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedForProjectCompletionYear Context triple: [CCTV Headquarters structural concept, usedForProjectCompletionYear, 2012]
-
A.
workCompletionYear
chosen
Indicates the calendar year in which a particular work, project, or task was completed.
-
B.
revisionCompletionYear
Indicates the year in which a revision of something (e.g., a work, document, or item) was completed.
-
C.
plannedEndYear
Indicates the calendar year in which an activity, project, or plan is intended or scheduled to be completed.
-
D.
originalCompletionYear
Indicates the year in which something (such as a project, work, or construction) was first fully completed.
-
E.
trainingCompletionYear
Indicates the calendar year in which an entity’s training program or course was completed.
- 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_69f348f1df848190851bbfb988da3414 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7b2f3a104819098ddd8909eaf596c |
completed | May 3, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f7b1b8a9fc8190a1279e67a2d12707 |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 1, 2026, 12:03 a.m.