Triple
T26882567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Courageous |
E676944
|
entity |
| Predicate | recommissionedAsAircraftCarrier |
P79377
|
FINISHED |
| Object | 1928 |
—
|
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: 1928 | Statement: [HMS Courageous, recommissionedAsAircraftCarrier, 1928]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recommissionedAsAircraftCarrier Context triple: [HMS Courageous, recommissionedAsAircraftCarrier, 1928]
-
A.
recommissionedAsCarrierYear
chosen
Indicates the year in which an entity was recommissioned specifically in the role or configuration of a carrier.
-
B.
capturedAndCommissioned
Indicates that one entity has taken control of another (often by force) and then formally put it into service or use under its authority.
-
C.
hasAircraftCarrier
Indicates that one entity possesses, operates, or includes an aircraft carrier as part of its assets or resources.
-
D.
aircraftCarrierOperatedFrom
Indicates that an aircraft carrier conducts its operations from, or is based at, a particular location or facility.
-
E.
aircraftCarrierInvolved
Indicates that an aircraft carrier participates in, is present at, or is otherwise directly involved in the specified event or situation.
- 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_69eee9bc0c90819085608c8bdc513a57 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f61f1e3cc48190aca708d4fd3668d6 |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f611ad2eb48190ac1ed0090f13f7a9 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 5:40 a.m.