Triple
T8593664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chinese Dream of national rejuvenation |
E203490
|
entity |
| Predicate | firstProposedIn |
P25813
|
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: [Chinese Dream of national rejuvenation, firstProposedIn, 2012]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstProposedIn Context triple: [Chinese Dream of national rejuvenation, firstProposedIn, 2012]
-
A.
originallyProposedFor
Indicates that something was first suggested, designed, or intended to be used for a particular purpose, context, or target.
-
B.
proposedInYear
chosen
Indicates that something, such as a plan, idea, or piece of legislation, was formally put forward or suggested in a specific calendar year.
-
C.
firstAppeared
Indicates the earliest known time or context in which an entity was introduced, observed, or came into existence.
-
D.
firstAppearedAt
Indicates the point in time or specific event at which an entity was first introduced, observed, or became known.
-
E.
firstPresentedFor
Indicates that one entity was initially introduced, submitted, or shown to another entity at a particular time or context.
- 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_69ca832a7f108190b4e4f5648abf4aa2 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc46c5e8888190b721e791c449b0df |
completed | March 31, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69cc454504448190aaad2af8b17357cd |
completed | March 31, 2026, 10:05 p.m. |
Created at: March 30, 2026, 6:23 p.m.