Triple
T31792555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | US-3A |
E811508
|
entity |
| Predicate | roleConversionFrom |
P172306
|
FINISHED |
| Object | anti-submarine warfare aircraft |
—
|
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 aircraft | Statement: [US-3A, roleConversionFrom, anti-submarine warfare aircraft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleConversionFrom Context triple: [US-3A, roleConversionFrom, anti-submarine warfare aircraft]
-
A.
covertRole
Indicates that an entity holds or performs a hidden, secret, or undercover role in relation to another entity or context.
-
B.
roleAfterConversion
Indicates the role or position an entity holds after undergoing a conversion, transition, or change from a previous state or role.
-
C.
roleTakenOverFrom
Indicates that one entity has assumed or inherited a role or position that was previously held by another entity.
-
D.
exportRole
Indicates that an entity functions in a capacity or role specifically related to exporting goods, services, or data.
-
E.
conversionRole
Indicates the specific role or function an entity plays within a conversion process or event.
- 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_69f348e60748819082dcaa7792659803 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6ac1a37908190a1ad8005a8e5d2ae |
completed | May 3, 2026, 1:59 a.m. |
| PD | Predicate disambiguation | batch_69f6aa21f2508190a204a424ffc00ca6 |
completed | May 3, 2026, 1:51 a.m. |
| PDg | Predicate description generation | batch_69f6aac95c1481909fff33702d0a6c37 |
completed | May 3, 2026, 1:54 a.m. |
Created at: April 30, 2026, 11:39 p.m.