Triple
T38135831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xinhai |
E952347
|
entity |
| Predicate | ISOYearCodeExample |
P109569
|
FINISHED |
| Object | 1911-辛亥 |
—
|
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: 1911-辛亥 | Statement: [Xinhai, ISOYearCodeExample, 1911-辛亥]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ISOYearCodeExample Context triple: [Xinhai, ISOYearCodeExample, 1911-辛亥]
-
A.
yearInGregorianCalendar
Indicates that a specified year is measured according to the Gregorian calendar system.
-
B.
specifiedYear
Indicates that a particular year has been explicitly designated or identified in relation to the subject.
-
C.
includesYear
chosen
Indicates that one entity contains, references, or is associated with a specific calendar year as part of its information or scope.
-
D.
serializationYear
Indicates the year in which a work, content, or data was serialized or released in serialized form.
-
E.
yearOfIdentification
Indicates the specific year in which an entity was first identified, discovered, or formally recognized.
- 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_69f76f09a7148190a4b91c0bacdc127a |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcb089a8f881909aa9e722babd43f7 |
completed | May 7, 2026, 3:32 p.m. |
| PD | Predicate disambiguation | batch_69fc45666c5c8190913bd632ac0e5b84 |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:21 p.m.