Triple
T17682132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lumley Lyster |
E440794
|
entity |
| Predicate | navalSpecialism |
P77974
|
FINISHED |
| Object | aircraft carrier operations |
—
|
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: aircraft carrier operations | Statement: [Lumley Lyster, navalSpecialism, aircraft carrier operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navalSpecialism Context triple: [Lumley Lyster, navalSpecialism, aircraft carrier operations]
-
A.
navalDiscipline
Indicates the enforcement or maintenance of rules, order, and conduct within a naval or maritime context.
-
B.
navalFeatures
Indicates that something possesses characteristics, components, or attributes specifically associated with naval or maritime contexts.
-
C.
navalTacticRole
Indicates the specific tactical function or role an entity performs within a naval operation or maritime combat context.
-
D.
hasNavalComponent
Indicates that something includes, involves, or is associated with a naval or maritime element as part of its composition or structure.
-
E.
navalOperations
chosen
Indicates involvement in planning, conducting, or supporting military activities carried out by naval forces at sea or from the sea.
- 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_69d8b9e940b081908b862bb0e6e89b0d |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4704514d481908aad4172fa930e6b |
completed | April 19, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_69e3cde3673c8190a889e14ba1f07dc1 |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 10:02 a.m.