Triple
T7381427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince of Lippe |
E170260
|
entity |
| Predicate | titleUseToday |
P29608
|
FINISHED |
| Object | head of the House of Lippe in German nobility |
—
|
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 Lippe in German nobility | Statement: [Prince of Lippe, titleUseToday, head of the House of Lippe in German nobility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleUseToday Context triple: [Prince of Lippe, titleUseToday, head of the House of Lippe in German nobility]
-
A.
titleUsage
chosen
Indicates how a title is applied, referenced, or used in relation to an entity or context.
-
B.
titleStart
Indicates that one entity’s title begins with the text or substring represented by the other entity.
-
C.
title
Indicates that one entity serves as the formal name or designation of another entity.
-
D.
titlePattern
Indicates that there is a specific structural or textual pattern that the title of an entity is expected to follow.
-
E.
titleTheme
Indicates that a work’s title reflects, expresses, or is thematically centered on a particular theme.
- 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_69c68a5d0ed08190b6d361e68f813330 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f1c7b5bc81908afa2bf39159979b |
completed | March 27, 2026, 9:08 p.m. |
| PD | Predicate disambiguation | batch_69c6f02ee3e08190a7a00c981129b22c |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:08 p.m.