Triple
T26983140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke of Västergötland |
E679657
|
entity |
| Predicate | isAdministrativeOffice |
P39747
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [Duke of Västergötland, isAdministrativeOffice, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAdministrativeOffice Context triple: [Duke of Västergötland, isAdministrativeOffice, no]
-
A.
administrativeOffice
chosen
Indicates that one entity serves as the administrative office or central administrative unit responsible for managing or overseeing the affairs of another entity.
-
B.
isPermanentOffice
Indicates that an office or position is established on a lasting, ongoing basis rather than being temporary or time-limited.
-
C.
officeIsIn
Indicates that one office is located within or inside another specified place or building.
-
D.
administrativelyIn
Indicates that one entity is located within or belongs to the jurisdiction or governance area of another entity for administrative purposes.
-
E.
isMajorOfficeBuildingIn
Indicates that a building is a primary or significant office structure located within a specified geographic or administrative area.
- 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_69eeeb5138ac8190b3c273ddc659a54f |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f62157d63c819096fd1addc0b960dc |
completed | May 2, 2026, 4:07 p.m. |
| PD | Predicate disambiguation | batch_69f611af72ac819094598dd2530d7411 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 6:47 a.m.