Triple
T25764359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Lexington (CV-16) |
E648836
|
entity |
| Predicate | rolePostWWII |
P45216
|
FINISHED |
| Object | anti-submarine warfare carrier |
—
|
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: anti-submarine warfare carrier | Statement: [USS Lexington (CV-16), rolePostWWII, anti-submarine warfare carrier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rolePostWWII Context triple: [USS Lexington (CV-16), rolePostWWII, anti-submarine warfare carrier]
-
A.
postWWIIRole
chosen
Indicates the role, position, or function an entity assumed or performed in the period following World War II.
-
B.
roleAfter1971
Indicates that an entity held a particular role or position at some point after the year 1971.
-
C.
roleDuringColdWar
Indicates the specific position, function, or involvement an entity had in the context of the Cold War period.
-
D.
statusAfterWWII
Indicates the condition, role, or classification an entity had following the end of World War II.
-
E.
roleAfterWar
Indicates the role or position an entity assumes following the end of a war or armed conflict.
- 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_69e7ab322db0819092d6a2b3d4572e01 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f5fdf1e3f88190b93219ed0b281fb2 |
completed | May 2, 2026, 1:36 p.m. |
| PD | Predicate disambiguation | batch_69f4a0fed15881909b789251fe5d8d45 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 22, 2026, 5:08 a.m.