Triple
T25735481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Fargo (CL-85) |
E645365
|
entity |
| Predicate | finalRoleAfterConversion |
P72233
|
FINISHED |
| Object | light aircraft 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: light aircraft carrier | Statement: [USS Fargo (CL-85), finalRoleAfterConversion, light aircraft carrier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalRoleAfterConversion Context triple: [USS Fargo (CL-85), finalRoleAfterConversion, light aircraft carrier]
-
A.
roleAfterConversion
chosen
Indicates the role or position an entity holds after undergoing a conversion, transition, or change from a previous state or role.
-
B.
finalPeriodRole
Indicates the role or function an entity holds during the final period or concluding phase of a specified interval or process.
-
C.
subsequentRole
Indicates that one role or position is held after, and in succession to, another role or position.
-
D.
conversionRole
Indicates the specific role or function an entity plays within a conversion process or event.
-
E.
afterConversionKnownAs
Indicates that an entity is referred to by a new name or identifier after undergoing a conversion or transformation.
- 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_69e77e85254081908d79ee4e8715f283 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f65aa07c048190a5df30d53d8f0cf5 |
completed | May 2, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f659cc571c819097e51e531961d812 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 21, 2026, 11:25 p.m.