Triple
T4833057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Count of Lippe |
E107989
|
entity |
| Predicate | nobleHouseOrigin |
P20125
|
FINISHED |
| Object | German princely house |
—
|
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: German princely house | Statement: [Count of Lippe, nobleHouseOrigin, German princely house]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nobleHouseOrigin Context triple: [Count of Lippe, nobleHouseOrigin, German princely house]
-
A.
motherNobleFamily
Indicates that a person’s mother belongs to a specified noble family or house.
-
B.
associatedNobleFamily
Indicates a relationship where an entity is linked or connected to a particular noble family, typically by heritage, allegiance, or formal association.
-
C.
dynasticOrigin
chosen
Indicates the historical dynasty or ruling family from which an entity originates or descends.
-
D.
nobleFamilySeat
Indicates the location that serves as the principal seat or main residence of a noble family.
-
E.
notableNobleFaction
Indicates that a noble is significantly associated with or belongs to a particularly prominent or influential noble faction.
- 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_69bd43fbe444819085cb970706ef73f7 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ff981fc819080d4466c6fe06cf3 |
completed | March 20, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69bd6c21c7f08190846049d31fdfa144 |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:24 p.m.