Triple
T3453168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stele Pavilion |
E72838
|
entity |
| Predicate | inscriptionsHonor |
P25839
|
FINISHED |
| Object | emperors buried in the Ming Tombs |
—
|
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: emperors buried in the Ming Tombs | Statement: [Stele Pavilion, inscriptionsHonor, emperors buried in the Ming Tombs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inscriptionsHonor Context triple: [Stele Pavilion, inscriptionsHonor, emperors buried in the Ming Tombs]
-
A.
inscriptionHonors
chosen
Indicates that an inscription is created to honor, commemorate, or pay tribute to a particular entity or event.
-
B.
nameHonors
Indicates that a name is given to honor, commemorate, or pay tribute to a particular entity.
-
C.
honoredThrough
Indicates that one entity is recognized or commemorated by means of another entity, event, or action.
-
D.
honors
Indicates that one entity shows respect, recognition, or esteem toward another entity, often in a formal or ceremonial way.
-
E.
artistHonored
Indicates that one entity has been formally recognized or celebrated in honor of an artist.
- 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_69ad85b12a908190a1d10a6b03b4f8ae |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adbaa457fc8190824ca00254e962f9 |
completed | March 8, 2026, 6:06 p.m. |
| PD | Predicate disambiguation | batch_69adae041d588190a84a02bca94adec8 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:16 p.m.