Triple
T26882558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Courageous |
E676944
|
entity |
| Predicate | laterClass |
P183705
|
FINISHED |
| Object | Courageous-class aircraft carrier |
—
|
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: Courageous-class aircraft carrier | Statement: [HMS Courageous, laterClass, Courageous-class aircraft carrier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterClass Context triple: [HMS Courageous, laterClass, Courageous-class aircraft carrier]
-
A.
laterBase
Indicates that one event, state, or version occurs or is valid at a later time than another referenced event, state, or version.
-
B.
laterSpecialization
Indicates that one entity becomes a more specialized or refined version of another entity at a later point in time.
-
C.
laterExtendedIn
Indicates that an existing entity (such as a work, version, or specification) was subsequently expanded, updated, or built upon by a later entity.
-
D.
laterInstanceOf
Indicates that one entity is a subsequent or later-occurring instance of the same type or pattern as another entity.
-
E.
laterNamed
Indicates that an entity was given a new name at a later time, linking its original identity to its subsequent name.
- 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_69eee9bc0c90819085608c8bdc513a57 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f7a283388c81908e4a9ee3369e8d6f |
completed | May 3, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
| PDg | Predicate description generation | batch_69f7a224365081908ff6958e3b30bd05 |
completed | May 3, 2026, 7:29 p.m. |
Created at: April 27, 2026, 5:40 a.m.