Triple
T27761038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cameroon Line |
E701467
|
entity |
| Predicate | continentalSegmentName |
P173228
|
FINISHED |
| Object | Cameroon Volcanic Line |
—
|
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: Cameroon Volcanic Line | Statement: [Cameroon Line, continentalSegmentName, Cameroon Volcanic Line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: continentalSegmentName Context triple: [Cameroon Line, continentalSegmentName, Cameroon Volcanic Line]
-
A.
continentMargin
Indicates that one entity lies along or forms the boundary region at the edge of a continental landmass relative to another entity.
-
B.
transcontinentalRegion
Indicates a region that spans or extends across more than one continent.
-
C.
partOfTranscontinentalRegion
Indicates that a region is a constituent part of a larger transcontinental region that spans more than one continent.
-
D.
continentalPortion
Indicates that one entity represents the part or portion of a continent to which the other entity belongs or is associated.
-
E.
continent
Indicates that one entity is a continent on which the other entity is geographically located or to which it belongs.
- F. None of above. chosen
Provenance (4 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_69ef6a5193808190816eb7d0020b2d87 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f6b342499c8190b85009a3f0f179e4 |
completed | May 3, 2026, 2:30 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
| PDg | Predicate description generation | batch_69f6b2a31e008190aacef03c2ebe5787 |
completed | May 3, 2026, 2:27 a.m. |
Created at: April 27, 2026, 4:27 p.m.