Triple
T4833065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Count of Lippe |
E107989
|
entity |
| Predicate | titleHereditary |
P1913
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Count of Lippe, titleHereditary, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleHereditary Context triple: [Count of Lippe, titleHereditary, true]
-
A.
hereditaryPeerage
chosen
Indicates that a person holds a noble title that is legally inheritable and passes down through family lineage.
-
B.
hasHereditaryChief
Indicates that an entity is led or governed by a chief whose position is inherited through family lineage.
-
C.
heirOf
Indicates that one entity is the legal or designated successor who inherits from another entity, typically upon that entity’s death or transfer of rights.
-
D.
higherTitleHeir
Indicates that the heir holds or is designated to inherit a title of higher rank or precedence than the compared title.
-
E.
inheritsTitle
Indicates that one entity receives and assumes a formal title or rank previously held by another entity, typically through succession or inheritance.
- 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.