Triple
T34793921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. consul in Glasgow, Scotland |
E1003016
|
entity |
| Predicate | hostNationSubunit |
P181893
|
FINISHED |
| Object | Scotland |
—
|
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: Scotland | Statement: [U.S. consul in Glasgow, Scotland, hostNationSubunit, Scotland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostNationSubunit Context triple: [U.S. consul in Glasgow, Scotland, hostNationSubunit, Scotland]
-
A.
hostNationBase
Indicates that one nation serves as the host country for a military or strategic base belonging to another entity.
-
B.
hostNationCapital
Indicates that a city serves as the capital of a particular host nation.
-
C.
hostNationInGroup
Indicates that a nation serving as the host of an event is assigned to or belongs within a particular group or pool in that event’s structure.
-
D.
hostNationRole
Indicates the role or capacity in which a nation serves as the host in a particular event, activity, or context.
-
E.
hostNationPavilion
Indicates that a pavilion is designated as the official pavilion of the host nation for a given event or exhibition.
- F. None of above. chosen
Provenance (4 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_69f76db543808190b188c6c86a91491b |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f782f4f10081908f97f6d0d2dbeec7 |
completed | May 3, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_69f780ff71cc8190a67e71076fbad81a |
completed | May 3, 2026, 5:08 p.m. |
| PDg | Predicate description generation | batch_69f782f416c081908bdd9b1ad456f0e2 |
completed | May 3, 2026, 5:16 p.m. |
Created at: May 3, 2026, 3:59 p.m.