Triple
T5881455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NOAA Ship Okeanos Explorer |
E130757
|
entity |
| Predicate | enteredServiceWithNOAA |
P24152
|
FINISHED |
| Object | 2008 |
—
|
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: 2008 | Statement: [NOAA Ship Okeanos Explorer, enteredServiceWithNOAA, 2008]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enteredServiceWithNOAA Context triple: [NOAA Ship Okeanos Explorer, enteredServiceWithNOAA, 2008]
-
A.
enteredService
Indicates that an entity began active use or operation at a specific time or in a specific context.
-
B.
enteredServiceWithUnit
chosen
Indicates that an entity began its period of service or active duty while assigned to a specified unit.
-
C.
enteredServiceAsHospitalShip
Indicates that an entity began operating in the role or capacity of a hospital ship from a specified point in time.
-
D.
referredAircraftEnteredService
Indicates that the aircraft being referenced has begun its operational service or has been officially placed into service.
-
E.
enteredPublicDomainInUS
Indicates that the subject work has lost its copyright protection and is legally in the public domain within the United States as of a specified time.
- 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_69c0085523688190bfd487479ce819e6 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c03fe07b7081909f8577ec3a9a1a8d |
completed | March 22, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69c0334bdc308190ad0d7199ab975588 |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 3:57 p.m.