Triple
T36832574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yongdingmen Gate Tower |
E910182
|
entity |
| Predicate | originalDynasty |
P205073
|
FINISHED |
| Object | Ming dynasty |
E35743
|
NE 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: Ming dynasty | Statement: [Yongdingmen Gate Tower, originalDynasty, Ming dynasty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalDynasty Context triple: [Yongdingmen Gate Tower, originalDynasty, Ming dynasty]
-
A.
nativeDynasty
Indicates that a dynasty is indigenous to, or originally from, the place or polity it rules or is associated with.
-
B.
traditionalDynasty
Indicates a relationship where a dynasty is recognized as traditional, typically long-established and rooted in customary or historical authority.
-
C.
founderDynasty
Indicates that an entity is the founding member or originator of a particular dynasty.
-
D.
creatorDynasty
Indicates the historical dynasty or ruling period during which the creator of an entity lived or was active.
-
E.
dominantDynasty
Indicates that one dynasty holds prevailing power, influence, or control over a given region or period relative to other dynasties.
- F. None of above. chosen
Provenance (5 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_69f76e7e9d60819092442fba73290a46 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3dde5d3ea08190be65acf490fdd1e4 |
completed | June 26, 2026, 2:05 a.m. |
| PD | Predicate disambiguation | batch_6a037a0e039481908a4a2666f76c5363 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82f8c88190bd77a086023ac0e1 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:13 p.m.