Triple
T32283834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Consulate General |
E824770
|
entity |
| Predicate | typicallyLocatedOutside |
P206241
|
FINISHED |
| Object | capital city |
—
|
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: capital city | Statement: [Consulate General, typicallyLocatedOutside, capital city]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicallyLocatedOutside Context triple: [Consulate General, typicallyLocatedOutside, capital city]
-
A.
isLocatedOnOutskirtsOf
Indicates that one entity is situated on the outer edge or peripheral area of another entity, rather than in its central or inner part.
-
B.
hasOutdoorLocation
Indicates that an entity is associated with or possesses a specific outdoor place or setting.
-
C.
isMostlyOutside
Indicates that one entity is located predominantly outside the boundaries or extent of another entity, with only a minor portion (if any) inside.
-
D.
isOutgroundOf
Indicates that one entity lies outside the boundary, extent, or coverage area defined by another entity.
-
E.
liesOutside
Indicates that one entity is located entirely beyond the spatial or conceptual boundary of another entity.
- 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_69f3490f404081908450db66884f4334 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379edf2d88190b492fca86ed23cac |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7fb9f88190b384b1b68200aef0 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 12:43 a.m.