Triple
T10100109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Mecklenburg-Strelitz |
E216176
|
entity |
| Predicate | presentHeadTitle |
P10091
|
FINISHED |
| Object | Head of the House of Mecklenburg-Strelitz |
—
|
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: Head of the House of Mecklenburg-Strelitz | Statement: [House of Mecklenburg-Strelitz, presentHeadTitle, Head of the House of Mecklenburg-Strelitz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: presentHeadTitle Context triple: [House of Mecklenburg-Strelitz, presentHeadTitle, Head of the House of Mecklenburg-Strelitz]
-
A.
currentHeadTitle
chosen
Indicates the official title or position currently held by the head or leader of an entity.
-
B.
titleRepresents
Indicates that a given title stands for, denotes, or symbolizes a particular concept, role, work, or entity.
-
C.
commonTitle
Indicates that two or more entities share the same title or designation.
-
D.
providedTitle
Indicates that one entity has supplied or assigned a specific title or designation to another entity.
-
E.
previousTitle
Indicates that one title held or used by an entity directly preceded another title in sequence or time.
- 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_69ca83d039f08190b9d10363221c69fb |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cdd07d686481908d9bb91392954474 |
completed | April 2, 2026, 2:12 a.m. |
| PD | Predicate disambiguation | batch_69cd4b9b853c8190a2af993ce9b21309 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:02 p.m.