Triple
T34267064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke of Turin |
E879196
|
entity |
| Predicate | hasDucalSeat |
P102016
|
FINISHED |
| Object | Turin |
—
|
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: Turin | Statement: [Duke of Turin, hasDucalSeat, Turin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDucalSeat Context triple: [Duke of Turin, hasDucalSeat, Turin]
-
A.
seatOfLiege
Indicates that a location serves as the primary seat or base of authority for a particular liege or ruling lord.
-
B.
hasSeatOfAdministration
Indicates that an administrative body or jurisdiction has a specific place or location that serves as its central seat of governance or administration.
-
C.
capitalOfDuchy
chosen
Indicates that a place serves as the capital city or administrative center of a particular duchy.
-
D.
isDiplomaticCenterOf
Indicates that a location serves as the primary site or hub for conducting diplomatic activities and relations for a specified entity.
-
E.
containsSeatOfMonarchy
Indicates that a place or region includes within its boundaries the official seat or residence of a monarchy’s ruling authority.
- 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_69f349b4f5fc819094b441d18e95e5f1 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71362f1448190985a80ce7af475cb |
completed | May 3, 2026, 9:20 a.m. |
| PD | Predicate disambiguation | batch_69f7127884388190884f23d181a65d19 |
completed | May 3, 2026, 9:16 a.m. |
Created at: May 1, 2026, 1:56 a.m.