Triple
T33755174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deep Sea Drilling Project |
E864957
|
entity |
| Predicate | usedResearchVessel |
P880
|
FINISHED |
| Object | Glomar Challenger |
—
|
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: Glomar Challenger | Statement: [Deep Sea Drilling Project, usedResearchVessel, Glomar Challenger]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedResearchVessel Context triple: [Deep Sea Drilling Project, usedResearchVessel, Glomar Challenger]
-
A.
researchVesselSurveys
Indicates that a research vessel conducts systematic surveys or data-collection activities on a specified area, subject, or target.
-
B.
usesVesselType
Indicates that an entity performs an activity or operation by employing a specific type or category of vessel.
-
C.
shipUsed
chosen
Indicates that a particular ship was employed or utilized in carrying out an event, activity, or operation.
-
D.
vesselTypeServedOn
Indicates the type of vessel on which an entity has served or performed duty.
-
E.
endTimeOfUseAsResearchVessel
Indicates the point in time when something’s role or function as a research vessel comes to an end.
- 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_69f3498c35f881909df279ae4270f831 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc5740fc81909774a4f65201a3ff |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:45 a.m.