Triple
T582374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ming Tombs |
E15084
|
entity |
| Predicate | DinglingExcavationPeriod |
P15783
|
FINISHED |
| Object | 1956–1958 |
—
|
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: 1956–1958 | Statement: [Ming Tombs, DinglingExcavationPeriod, 1956–1958]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: DinglingExcavationPeriod Context triple: [Ming Tombs, DinglingExcavationPeriod, 1956–1958]
-
A.
occupationPeriod
Indicates the time span during which an entity holds or held a particular occupation or role.
-
B.
culturalPeriod
Indicates the historical or cultural era with which an entity is associated or during which it was created, used, or significant.
-
C.
excavatedBy
Indicates that something (typically an archaeological site, artifact, or geological feature) was uncovered or dug out by a particular agent (such as a person, team, or organization).
-
D.
dominantDynasty
Indicates that one dynasty holds prevailing power, influence, or control over a given region or period relative to other dynasties.
-
E.
chronologyWithinReignOf
Indicates that one event or time period occurs entirely within the span of a specified ruler’s reign.
- F. None of above. chosen
Provenance (4 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_69a4935783b8819082b77726ec10cc42 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49b85becc8190b4d98c00e5fa7c04 |
completed | March 1, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69a494c7f9008190bd8d05b4dc2a7c7f |
completed | March 1, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69a4985a2d08819090947895d9439e06 |
completed | March 1, 2026, 7:49 p.m. |
Created at: March 1, 2026, 7:33 p.m.