Triple
T24134718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Limburg-Styrum-Runkel branch |
E598050
|
entity |
| Predicate | houseNameElement |
P138201
|
FINISHED |
| Object | Limburg-Styrum |
—
|
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: Limburg-Styrum | Statement: [Limburg-Styrum-Runkel branch, houseNameElement, Limburg-Styrum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: houseNameElement Context triple: [Limburg-Styrum-Runkel branch, houseNameElement, Limburg-Styrum]
-
A.
houseName
Indicates the specific name or designation assigned to a house.
-
B.
houseElement
chosen
Indicates that one entity is a structural or functional component of a house associated with another entity.
-
C.
houseNickname
Indicates that an entity has an informal or alternative name used as a nickname for a house or dwelling.
-
D.
houseHead
Indicates that one entity serves as the head, leader, or primary authority of a particular house or household associated with the other entity.
-
E.
homeFieldName
Indicates the name of the field or venue that serves as an entity’s home location for its activities or events.
- 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_69e288c92e448190ac57034fa0c863ce |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1df7b6e9c819097fb546efa35821b |
completed | April 29, 2026, 10:37 a.m. |
| PD | Predicate disambiguation | batch_69f1765650fc8190a6bc1eb512b240bf |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:26 p.m.