Triple
T30815378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iglesia de San Francisco Javier |
E784759
|
entity |
| Predicate | hasMainSquareConnection |
P129644
|
FINISHED |
| Object | Plaza Mayor de Cáceres |
—
|
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: Plaza Mayor de Cáceres | Statement: [Iglesia de San Francisco Javier, hasMainSquareConnection, Plaza Mayor de Cáceres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainSquareConnection Context triple: [Iglesia de San Francisco Javier, hasMainSquareConnection, Plaza Mayor de Cáceres]
-
A.
citySquareConnected
Indicates that two locations are directly linked or accessible to each other via a city square.
-
B.
isMainCeremonialSquareOf
Indicates that a particular square serves as the primary official or ceremonial public space for a given place or community.
-
C.
mainSquare
Indicates that a location serves as the primary or central public square of a town or city.
-
D.
hasPublicSquareInFront
chosen
Indicates that a building or structure has a public square located directly in front of it.
-
E.
hasPromenadeConnection
Indicates that two locations are linked by a promenade, such as a walkway or pedestrian route, allowing movement or access between them.
- 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_69f224b4eda48190bd212ce4f3901e56 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ffcc6182b48190afb598ced6500e66 |
completed | May 10, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69ffcbb363748190bc6f8d038fba44ff |
completed | May 10, 2026, 12:05 a.m. |
Created at: April 29, 2026, 8:43 p.m.