Triple
T30440693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GBFXT |
E774431
|
entity |
| Predicate | locatesIn |
P40
|
FINISHED |
| Object | United Kingdom |
—
|
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: United Kingdom | Statement: [GBFXT, locatesIn, United Kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatesIn Context triple: [GBFXT, locatesIn, United Kingdom]
-
A.
locates
Indicates that one entity determines, specifies, or identifies the position or place of another entity in space or within a given context.
-
B.
locatedIn
chosen
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
-
C.
sometimesLocatedIn
Indicates that an entity is located in a given place only at certain times or under certain conditions, rather than permanently or always.
-
D.
hasLocationsIn
Indicates that an entity maintains a presence, operations, or facilities in one or more specified geographic locations.
-
E.
locatedWith
Indicates that two or more entities are situated together in the same place or spatial context.
- 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_69f22493ef9c8190ae8c2afcb7f994c8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a00bc079314819096271bba60bee52d |
completed | May 10, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_6a00bba5bd408190ace5db0c4a90dc6f |
completed | May 10, 2026, 5:08 p.m. |
Created at: April 29, 2026, 8:08 p.m.