Triple
T19618604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamato dynasty |
E470932
|
entity |
| Predicate | hasFemaleRulers |
P48170
|
FINISHED |
| Object | yes (historically several reigning empresses) |
—
|
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: yes (historically several reigning empresses) | Statement: [Yamato dynasty, hasFemaleRulers, yes (historically several reigning empresses)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFemaleRulers Context triple: [Yamato dynasty, hasFemaleRulers, yes (historically several reigning empresses)]
-
A.
hasFemaleLeader
chosen
Indicates that the subject entity is led or governed by a woman in a primary leadership role.
-
B.
hasNumberOfRulers
Indicates the quantity of rulers associated with or governing a given entity.
-
C.
kingdomRuledByHerFather
Indicates that a kingdom is governed or ruled by the father of a specified person.
-
D.
hasFamousRuler
Indicates that an entity is or was ruled by a ruler who is widely recognized or historically notable.
-
E.
recognizedAsRulersBy
Indicates that certain entities are acknowledged or accepted by others as their legitimate rulers or authorities.
- 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_69d8e510fa248190b7afb274a1d4cf73 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e640e4570c81909fc4f9b871346337 |
completed | April 20, 2026, 3:06 p.m. |
| PD | Predicate disambiguation | batch_69e514e5cb108190ae260e466c447314 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:43 p.m.