Triple
T36874735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ofqui Isthmus |
E911312
|
entity |
| Predicate | landBridgeBetween |
P186633
|
FINISHED |
| Object | Gulf of Penas |
E75035
|
NE 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: Gulf of Penas | Statement: [Ofqui Isthmus, landBridgeBetween, Gulf of Penas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: landBridgeBetween Context triple: [Ofqui Isthmus, landBridgeBetween, Gulf of Penas]
-
A.
bridgesBetween
Indicates a relationship where something connects or links two otherwise separate entities, contexts, or states, enabling interaction or transition between them.
-
B.
bridgeLocation
Indicates the specific place or area where a bridge is situated or spans.
-
C.
bridgeComponent
Indicates that one entity functions as a structural or functional component of a bridge associated with another entity.
-
D.
hasBridgeTo
Indicates that one entity is connected to another by a bridge or bridging structure that allows passage or linkage between them.
-
E.
bridgeFeature
Indicates that one entity functions as a structural or functional feature of a bridge associated with another entity.
- F. None of above. chosen
Provenance (5 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_69f76e82339881909607a65c0503d941 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fe1a1ca4819084c196f0041f0be2 |
completed | May 5, 2026, 2:26 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3e161dbf74819083712e5038938e3b |
completed | June 26, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_69f7cf7890008190a8bc355ff2d61c86 |
completed | May 3, 2026, 10:43 p.m. |
| PDg | Predicate description generation | batch_69f9fd66eed48190bdc26a8def328c2d |
completed | May 5, 2026, 2:23 p.m. |
Created at: May 3, 2026, 4:13 p.m.