Triple
T17111470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coat of arms of Cuba |
E415234
|
entity |
| Predicate | upperFieldDepicts |
P120766
|
FINISHED |
| Object | sea channel between two capes |
—
|
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: sea channel between two capes | Statement: [Coat of arms of Cuba, upperFieldDepicts, sea channel between two capes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: upperFieldDepicts Context triple: [Coat of arms of Cuba, upperFieldDepicts, sea channel between two capes]
-
A.
upperFieldCharge
Indicates that an entity has an electric charge located or defined in its upper field region.
-
B.
overField
Indicates a spatial relationship where one entity is positioned above or extends across the area of a field.
-
C.
upperComponent
chosen
Indicates that one component is positioned above or on top of another component within a larger structure or assembly.
-
D.
above
Indicates that one entity is positioned higher than another along a vertical axis, without implying direct contact.
-
E.
upperLevels
Indicates that one entity occupies or corresponds to higher levels, tiers, or hierarchical positions relative to another entity.
- 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_69d886d090cc8190a39cb94992586905 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dc2a7f2c81908eb19594b6accab7 |
completed | April 18, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69e35d6b1b988190a8d6b6fe78c35e59 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:35 a.m.