Triple
T6647607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ernest Shackleton |
E150740
|
entity |
| Predicate | joinedMerchantNavy |
P72025
|
FINISHED |
| Object | 1890 |
—
|
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: 1890 | Statement: [Ernest Shackleton, joinedMerchantNavy, 1890]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: joinedMerchantNavy Context triple: [Ernest Shackleton, joinedMerchantNavy, 1890]
-
A.
shipCommissionedAs
Indicates that a ship entered active service under a specific name or designation at the time of its commissioning.
-
B.
enteredRoyalNavyFrontlineService
Indicates that an entity began active duty or operational deployment in the frontline forces of the Royal Navy.
-
C.
strickenFromNavalRegister
Indicates that a vessel has been officially removed from a navy’s active register, ending its status as a commissioned naval ship.
-
D.
navy
Indicates that an entity serves as or is associated with a nation's naval military force.
-
E.
hasNavalComponent
Indicates that something includes, involves, or is associated with a naval or maritime element as part of its composition or structure.
- 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_69c687f1a3048190828b7342f7125d5c |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6cc9c6cb0819084fec8e0beb430de |
completed | March 27, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_69c6ad04d66c8190926ffcbff372643b |
completed | March 27, 2026, 4:15 p.m. |
| PDg | Predicate description generation | batch_69c6cc988c0081909d22b86ca299331c |
completed | March 27, 2026, 6:29 p.m. |
Created at: March 27, 2026, 2 p.m.