Triple
T21474997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fortín de San Gerónimo |
E529835
|
entity |
| Predicate | commandedApproachTo |
P17766
|
FINISHED |
| Object | eastern entrance to San Juan |
—
|
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: eastern entrance to San Juan | Statement: [Fortín de San Gerónimo, commandedApproachTo, eastern entrance to San Juan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commandedApproachTo Context triple: [Fortín de San Gerónimo, commandedApproachTo, eastern entrance to San Juan]
-
A.
approachControl
Indicates that one entity moves closer to another entity in a deliberate or controlled manner.
-
B.
commandedTo
chosen
Indicates that one entity has issued an order or directive for another entity to perform a specific action or fulfill a particular duty.
-
C.
usedToApproach
Indicates that one entity employed another entity as a means or method to move closer to or reach a target entity or location.
-
D.
hasInstrumentApproach
Indicates that an approach procedure to a location or runway is conducted using specified navigation instruments or instrument-based methods.
-
E.
hasApproachControl
Indicates that one entity exercises approach control authority or responsibility over another entity, typically managing its approach phase or access.
- 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_69e0c459acb481909bb6ee452a0045c7 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea1650788190bd55ebdbf1dfc46f |
completed | April 23, 2026, 9:44 a.m. |
| PD | Predicate disambiguation | batch_69e631ec1d048190b6da97da8222e413 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:19 p.m.