Triple
T29685665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Ocean Discovery Program |
E751075
|
entity |
| Predicate | usesResearchVessel |
P11945
|
FINISHED |
| Object | JOIDES Resolution |
—
|
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: JOIDES Resolution | Statement: [International Ocean Discovery Program, usesResearchVessel, JOIDES Resolution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesResearchVessel Context triple: [International Ocean Discovery Program, usesResearchVessel, JOIDES Resolution]
-
A.
researchVesselSurveys
Indicates that a research vessel conducts systematic surveys or data-collection activities on a specified area, subject, or target.
-
B.
hasResearchVesselsHomeport
Indicates that a location serves as the primary homeport or base of operations for one or more research vessels.
-
C.
governmentVessel
Indicates that the vessel is owned, operated, or officially designated for use by a government or governmental authority.
-
D.
usesVesselType
chosen
Indicates that an entity performs an activity or operation by employing a specific type or category of vessel.
-
E.
vesselTypeServedOn
Indicates the type of vessel on which an entity has served or performed duty.
- 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_69f0d625b09481909b0b69aea1e846c8 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f6a8df16a88190a23820e64a3b1f92 |
completed | May 3, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 28, 2026, 7:13 p.m.