Triple
T14062078
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zhizheng |
E338369
|
entity |
| Predicate | eraNumbering |
P3378
|
FINISHED |
| Object | Zhizheng 1 corresponds to 1341 |
—
|
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: Zhizheng 1 corresponds to 1341 | Statement: [Zhizheng, eraNumbering, Zhizheng 1 corresponds to 1341]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eraNumbering Context triple: [Zhizheng, eraNumbering, Zhizheng 1 corresponds to 1341]
-
A.
legalNumbering
Indicates that an entity has an officially assigned legal or regulatory identification number.
-
B.
numberingType
chosen
Indicates the scheme or style used to assign sequential numbers or labels within an ordered set.
-
C.
numberingDirection
Indicates the direction or order in which items are sequentially numbered within a set or structure.
-
D.
standardNumberingScheme
Indicates that there is a specific, commonly accepted numbering system or convention being applied to identify or order the related entities.
-
E.
numberingStatus
Indicates the status or condition of an entity’s assigned number or numbering process (e.g., whether it has been numbered, is pending, or has a particular numbering state).
- 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_69d81c67ba6c819091935650dfb3b895 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de568876308190840361dcaf10bd45 |
completed | April 14, 2026, 3 p.m. |
| PD | Predicate disambiguation | batch_69de05adef888190b023ab42ef5076b6 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:21 p.m.