Triple
T32029971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teck |
E817927
|
entity |
| Predicate | connectedDynasticallyTo |
P95093
|
FINISHED |
| Object | House of Württemberg |
—
|
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: House of Württemberg | Statement: [Teck, connectedDynasticallyTo, House of Württemberg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectedDynasticallyTo Context triple: [Teck, connectedDynasticallyTo, House of Württemberg]
-
A.
dynamicallyLinkedTo
Indicates that one entity is connected to another through a runtime-established link whose existence or configuration can change during execution.
-
B.
dynasticallyLinkedTo
chosen
Indicates a relationship where two entities are connected through a line of succession, inheritance, or familial rule within or across dynasties.
-
C.
connectsTo
Indicates a relationship where one entity is linked or joined to another, allowing interaction, communication, or transfer between them.
-
D.
partlyConnectedBy
Indicates that two entities are linked or joined by something in an incomplete, partial, or not fully continuous way.
-
E.
connectedByStraitTo
Indicates that one entity is geographically linked to another by a narrow body of water known as a strait.
- 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_69f348fbc8148190b3c0f95d4772b153 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69feb8e856d48190aa34ad8ee8376e1c |
completed | May 9, 2026, 4:32 a.m. |
| PD | Predicate disambiguation | batch_69feb82a2b6c8190a473cc25976897be |
completed | May 9, 2026, 4:29 a.m. |
Created at: May 1, 2026, 12:18 a.m.