Triple
T3534889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beaufort continental slope |
E74746
|
entity |
| Predicate | hasRelevanceFor |
P1887
|
FINISHED |
| Object | hydrocarbon exploration |
—
|
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: hydrocarbon exploration | Statement: [Beaufort continental slope, hasRelevanceFor, hydrocarbon exploration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRelevanceFor Context triple: [Beaufort continental slope, hasRelevanceFor, hydrocarbon exploration]
-
A.
relatedTo
Indicates a general, non-specific relationship or association exists between two entities.
-
B.
refersSpecificallyTo
Indicates that one entity makes an explicit, precise reference to another particular entity, distinguishing it from more general or ambiguous references.
-
C.
isImportantFor
chosen
Indicates that something holds significant value, relevance, or necessity in relation to something else.
-
D.
hasParticularSignificanceFor
Indicates that something holds a special, notable, or contextually important relevance or impact for a particular entity or situation.
-
E.
hasNotableReference
Indicates that one entity makes a significant or noteworthy mention of, or allusion 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_69ad85d1a3948190931fd1ea1f49717b |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbc9cff5c81909011f34c9bf28e11 |
completed | March 8, 2026, 6:14 p.m. |
| PD | Predicate disambiguation | batch_69adae13ab808190a5d6ecdc7543445e |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:19 p.m.