Triple
T15313326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Octopus |
E366091
|
entity |
| Predicate | typeOfExplorationEquipment |
P118071
|
FINISHED |
| Object | submersibles |
—
|
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: submersibles | Statement: [Octopus, typeOfExplorationEquipment, submersibles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfExplorationEquipment Context triple: [Octopus, typeOfExplorationEquipment, submersibles]
-
A.
typeOfEquipmentUsed
Indicates that a particular piece or category of equipment is utilized in performing a specific action, process, or activity.
-
B.
explorationType
Indicates the specific kind or category of exploration activity associated with an entity or event.
-
C.
missionEquipment
Indicates that certain equipment is assigned to, used for, or associated with carrying out a specific mission.
-
D.
equipmentTypeTrainedOn
Indicates the type of equipment on which an entity has received training or is qualified to operate.
-
E.
equippedFor
Indicates that one entity is suitably provided with the necessary tools, features, or capabilities to perform a particular function or handle a specific situation for another entity or purpose.
- 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_69d85a113ee881908e297a1d38dd79fa |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03dd050108190a584543cb93943a4 |
completed | April 16, 2026, 1:39 a.m. |
| PD | Predicate disambiguation | batch_69deca935e2c8190b640987ddfc542b9 |
completed | April 14, 2026, 11:15 p.m. |
| PDg | Predicate description generation | batch_69decf2e413481909d9180a8d78d2c17 |
completed | April 14, 2026, 11:35 p.m. |
Created at: April 10, 2026, 3:16 a.m.