Triple
T31831617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Principality of Leiningen |
E812551
|
entity |
| Predicate | hasMonarchFrom |
P196092
|
FINISHED |
| Object | House 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: House of Leiningen | Statement: [Principality of Leiningen, hasMonarchFrom, House of Leiningen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMonarchFrom Context triple: [Principality of Leiningen, hasMonarchFrom, House of Leiningen]
-
A.
monarchIs
Indicates that one entity serves as the ruling monarch (such as king, queen, or equivalent sovereign) of another entity, typically a state or territory.
-
B.
monarchIn
Indicates that a person serves as the ruling monarch of a specified country, state, or territory.
-
C.
appliedToMonarch
Indicates that an action, policy, or attribute is directed toward or exercised upon a monarch.
-
D.
monarchWhoGrants
Indicates a relationship where a monarch bestows, confers, or grants something (such as rights, titles, lands, or privileges) to another party.
-
E.
receivesMonarchsFrom
Indicates that one entity is the destination or recipient of monarchs that come or are sent from another entity.
- F. None of above. chosen
Provenance (4 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_69f348ea7ffc8190a2ab43d80277cf59 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fe066d62b48190867df334039be786 |
completed | May 8, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69fe03afde3c8190a5b9b0778d19eb1a |
completed | May 8, 2026, 3:39 p.m. |
| PDg | Predicate description generation | batch_69fe066b623c819085205fbea901e3cf |
completed | May 8, 2026, 3:51 p.m. |
Created at: April 30, 2026, 11:47 p.m.