Triple
T7185835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Villa de Leyva |
E167568
|
entity |
| Predicate | PlazaMayorSize |
P75888
|
FINISHED |
| Object | one of the largest town squares in Colombia |
—
|
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: one of the largest town squares in Colombia | Statement: [Villa de Leyva, PlazaMayorSize, one of the largest town squares in Colombia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: PlazaMayorSize Context triple: [Villa de Leyva, PlazaMayorSize, one of the largest town squares in Colombia]
-
A.
mainSquare
Indicates that a location serves as the primary or central public square of a town or city.
-
B.
hasPlaza
Indicates that an entity includes, contains, or is associated with a plaza as part of its structure or grounds.
-
C.
hasPedestrianPlazaOn
Indicates that a pedestrian plaza is located on, or directly associated with, a specified surface, structure, or area.
-
D.
lengthOfMainBuilding
Indicates the measured physical length of the main building in the context of a larger structure or site.
-
E.
isLargestParkOf
Indicates that a park is the largest park within a specified area, region, or administrative 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_69c6888a7c548190a3d39b52a393080f |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e9b045c48190b27b2d6f7c11026f |
completed | March 27, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69c6e74fb0f48190b2ad4dd4efdd241a |
completed | March 27, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69c6e9aeb1b08190ace6f978387c89aa |
completed | March 27, 2026, 8:33 p.m. |
Created at: March 27, 2026, 2:49 p.m.