Triple
T30594280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Miguel de Gualdape |
E778742
|
entity |
| Predicate | coordinateLocationStatus |
P34406
|
FINISHED |
| Object | unknown |
—
|
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: unknown | Statement: [San Miguel de Gualdape, coordinateLocationStatus, unknown]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coordinateLocationStatus Context triple: [San Miguel de Gualdape, coordinateLocationStatus, unknown]
-
A.
coordinateLocation
Indicates that an entity is located at, or associated with, a specific geographic coordinate or set of coordinates.
-
B.
locationStatus
chosen
Indicates the current state or condition of an entity with respect to a specific location (e.g., present, absent, en route, or unknown).
-
C.
coordinateStatus
Indicates that one entity’s status is aligned, synchronized, or made consistent with another entity’s status or with a shared reference state.
-
D.
coordinatesUseOf
Indicates that one entity organizes and manages the collaborative use or deployment of another entity’s resources, actions, or functions.
-
E.
hasCoordinateStatus
Indicates that two or more entities share the same hierarchical or organizational level within a given structure or system.
- 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_69f224a1570c8190a85d3ac330479a79 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6b967d5308190bbb66d0a8dd52612 |
completed | May 3, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
Created at: April 29, 2026, 8:24 p.m.