Triple
T38109481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Libertad Department, El Salvador |
E951613
|
entity |
| Predicate | capitalProximityTo |
P41518
|
FINISHED |
| Object | San Salvador |
—
|
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: San Salvador | Statement: [La Libertad Department, El Salvador, capitalProximityTo, San Salvador]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capitalProximityTo Context triple: [La Libertad Department, El Salvador, capitalProximityTo, San Salvador]
-
A.
isNearCapitalCity
Indicates that an entity is located close to, or in the immediate vicinity of, a capital city.
-
B.
distanceFromRegionalCapital
Indicates the measured spatial distance between a given place and its corresponding regional capital.
-
C.
hasUrbanProximity
Indicates that one entity is located near or within easy access to an urban area associated with another entity.
-
D.
stateCapitalProximity
Indicates the spatial closeness or distance between a state’s capital city and another specified location.
-
E.
regionCapitalNearby
chosen
Indicates that a capital city of a region is located close to the referenced place or entity.
- 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_69f76f065ed08190bdfb1b6d817f5b39 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fe610e1f6881908f10070ba64643cf |
completed | May 8, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69fe604c6c008190ad659e9b9fa82f7b |
completed | May 8, 2026, 10:14 p.m. |
Created at: May 3, 2026, 4:21 p.m.