Triple
T25269332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baron Inveraray |
E633520
|
entity |
| Predicate | hasSeatTown |
P15510
|
FINISHED |
| Object | Inveraray |
—
|
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: Inveraray | Statement: [Baron Inveraray, hasSeatTown, Inveraray]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeatTown Context triple: [Baron Inveraray, hasSeatTown, Inveraray]
-
A.
homeCityIsSeatOf
Indicates that the person’s home city serves as the administrative or governmental seat (e.g., capital) of a larger region such as a state, province, or country.
-
B.
alsoSeatOf
Indicates that a location serves as an additional or alternative seat (e.g., of government, administration, or authority) alongside another primary seat.
-
C.
hasTown
Indicates that one entity possesses, contains, or is associated with a town as part of its structure, jurisdiction, or composition.
-
D.
municipalitySeat
chosen
Indicates that one entity serves as the administrative center or capital (seat) of a municipality.
-
E.
hasSeatAt
Indicates that an entity occupies or holds a place, position, or membership within a specific group, body, or location.
- 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_69e75a92f48881909974ff9c11150a2e |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 21, 2026, 1:16 p.m.