Triple
T27761034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cameroon Line |
E701467
|
entity |
| Predicate | nearbyTectonicFeature |
P52075
|
FINISHED |
| Object | Benue Trough |
—
|
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: Benue Trough | Statement: [Cameroon Line, nearbyTectonicFeature, Benue Trough]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyTectonicFeature Context triple: [Cameroon Line, nearbyTectonicFeature, Benue Trough]
-
A.
isPartOfTectonicFeature
Indicates that one geological entity is a component or subdivision of a larger tectonic feature or structure.
-
B.
nearGeologicalSite
chosen
Indicates that one entity is located in close physical proximity to a geological site or feature.
-
C.
isTectonicFeature
Indicates that something is a geological structure or formation resulting from tectonic processes or plate movements.
-
D.
tectonicActivityCharacteristic
Indicates a characteristic or property that describes the nature, intensity, or pattern of tectonic activity associated with something.
-
E.
tectonicFeaturesPresence
Indicates the existence or occurrence of tectonic features (such as faults, folds, or plate boundaries) in a specified area or context.
- 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_69ef6a5193808190816eb7d0020b2d87 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f7764ab1fc81909f9348db87bd7692 |
completed | May 3, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69f76905d9c88190b1ee810bc9ab644f |
completed | May 3, 2026, 3:25 p.m. |
Created at: April 27, 2026, 4:27 p.m.