Triple
T28795479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lê dynasty |
E727073
|
entity |
| Predicate | deFactoRulersDuringRestoredPeriod |
P61442
|
FINISHED |
| Object | Trịnh lords |
—
|
NE NERFINISHED |
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: Trịnh lords | Statement: [Lê dynasty, deFactoRulersDuringRestoredPeriod, Trịnh lords]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deFactoRulersDuringRestoredPeriod Context triple: [Lê dynasty, deFactoRulersDuringRestoredPeriod, Trịnh lords]
-
A.
deFactoRulersDuringReign
chosen
Indicates that the referenced entities were the actual, effective rulers exercising power during the nominal reign of another ruler.
-
B.
coRulership
Indicates a relationship in which two or more entities share authority or power to rule jointly over the same domain or group.
-
C.
historicalRulers
Indicates that one entity has served as a ruler or governing authority over the other entity at some point in history.
-
D.
recognizedAsRulersBy
Indicates that certain entities are acknowledged or accepted by others as their legitimate rulers or authorities.
-
E.
periodOfRule
Indicates the span of time during which an entity exercised authority, control, or governance over something.
- 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_69f0319b7c44819085736bcc256185e6 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f658ee40088190b71e1219407690d0 |
completed | May 2, 2026, 8:05 p.m. |
| PD | Predicate disambiguation | batch_69f65760fd3081908ffe014a5e2bf069 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:25 a.m.