Triple
T5208692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vøring Plateau |
E117573
|
entity |
| Predicate | investigatedUsing |
P62028
|
FINISHED |
| Object | seismic reflection data |
—
|
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: seismic reflection data | Statement: [Vøring Plateau, investigatedUsing, seismic reflection data]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: investigatedUsing Context triple: [Vøring Plateau, investigatedUsing, seismic reflection data]
-
A.
investigatedFor
Indicates that an entity is the subject of an investigation concerning a suspected involvement in another entity (typically a crime, incident, or wrongdoing).
-
B.
investigatedBy
Indicates that an entity is the subject of an investigation carried out by another entity.
-
C.
usesInvestigativeMethods
Indicates that an entity employs investigative techniques or procedures to gather information, analyze evidence, or uncover facts.
-
D.
investigatedEvent
Indicates that an event was the subject of an investigation or inquiry carried out by some agent.
-
E.
investigativeFocus
Indicates that an entity is the primary subject or target of investigation, inquiry, or detailed scrutiny by another entity.
- 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_69bd4463dd3c81909966123f20b79d57 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7a6f0ffc819090b8b59fc22f4dae |
completed | March 20, 2026, 4:48 p.m. |
| PD | Predicate disambiguation | batch_69bd77bb4e8c819094b5ac7cf61512f9 |
completed | March 20, 2026, 4:37 p.m. |
| PDg | Predicate description generation | batch_69bd79000cf88190b3c05d95395b0cd2 |
completed | March 20, 2026, 4:42 p.m. |
Created at: March 20, 2026, 1:47 p.m.