Triple
T11208712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vega Alta |
E265244
|
entity |
| Predicate | hasNeighboringContext |
P75455
|
FINISHED |
| Object | near San Juan metropolitan core |
—
|
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: near San Juan metropolitan core | Statement: [Vega Alta, hasNeighboringContext, near San Juan metropolitan core]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNeighboringContext Context triple: [Vega Alta, hasNeighboringContext, near San Juan metropolitan core]
-
A.
hasNeighbouringState
Indicates that one state shares a common border or is directly adjacent geographically to another state.
-
B.
hasAdjacentUse
Indicates that one entity is used or occurs directly next to another in space, time, or sequence.
-
C.
hasNeighborhoodAlong
Indicates that one entity has a neighboring area or region that extends along the boundary or length of another entity.
-
D.
hasNeighbouringQuarter
Indicates that one quarter (district or area) is directly adjacent to and shares a boundary with another quarter.
-
E.
neighboringTo
chosen
Indicates that one entity is located directly adjacent or very close to another entity, sharing a common boundary or immediate vicinity.
- 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_69d6aac59460819089b9848b27f57848 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8d5f8908190903817f84c629ba1 |
completed | April 9, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69d75cf83464819087529d47d025d313 |
completed | April 9, 2026, 8:02 a.m. |
Created at: April 8, 2026, 9:30 p.m.