Triple
T13171707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tupolev Tu-98 |
E312990
|
entity |
| Predicate | operationalService |
P108880
|
FINISHED |
| Object | never entered regular squadron service |
—
|
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: never entered regular squadron service | Statement: [Tupolev Tu-98, operationalService, never entered regular squadron service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operationalService Context triple: [Tupolev Tu-98, operationalService, never entered regular squadron service]
-
A.
globalServiceOperational
Indicates that a service is currently functioning and available across all intended global regions or locations.
-
B.
operatesService
Indicates that an agent runs, manages, or provides a particular service.
-
C.
ledToOperationalServiceOf
Indicates that one entity caused or enabled another entity to enter or begin operational service.
-
D.
regionalServiceOperational
Indicates that a service is currently functioning and available within a specified geographic region.
-
E.
operatesServiceTo
Indicates that one entity runs or provides a transportation or service route to another entity or location.
- 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_69d806ac3ee081909b2fd27d060aa974 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bc2c0c88190be357811aa8e828d |
completed | April 10, 2026, 11:46 p.m. |
| PDg | Predicate description generation | batch_69d98ceeb22c8190a6be666031d9e5a4 |
completed | April 10, 2026, 11:51 p.m. |
Created at: April 9, 2026, 9:13 p.m.