Triple
T31503889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Altleiningen |
E803761
|
entity |
| Predicate | hasHistoricalRulers |
P8531
|
FINISHED |
| Object | Counts of Leiningen |
—
|
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: Counts of Leiningen | Statement: [Altleiningen, hasHistoricalRulers, Counts of Leiningen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricalRulers Context triple: [Altleiningen, hasHistoricalRulers, Counts of Leiningen]
-
A.
historicalRulers
chosen
Indicates that one entity has served as a ruler or governing authority over the other entity at some point in history.
-
B.
hasNumberOfRulers
Indicates the quantity of rulers associated with or governing a given entity.
-
C.
hasFamousRuler
Indicates that an entity is or was ruled by a ruler who is widely recognized or historically notable.
-
D.
hasRulingPeople
Indicates that a group or entity serves as the governing or ruling authority over another entity.
-
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_69f348cae52081909fa8e5f697523ae3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fe21b0cba48190b56c39e9f1c0eafa |
completed | May 8, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69fe204576848190aecf204e2adba5dc |
completed | May 8, 2026, 5:41 p.m. |
Created at: April 30, 2026, 9:46 p.m.