Triple
T34300034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PL-15 |
E880143
|
entity |
| Predicate | designedForPlatformGeneration |
P81855
|
FINISHED |
| Object | 4.5-generation fighters |
—
|
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: 4.5-generation fighters | Statement: [PL-15, designedForPlatformGeneration, 4.5-generation fighters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedForPlatformGeneration Context triple: [PL-15, designedForPlatformGeneration, 4.5-generation fighters]
-
A.
targetPlatformGeneration
chosen
Indicates the generation or version of the platform that an action, resource, or entity is specifically intended to run on or be compatible with.
-
B.
originalPlatformGeneration
Indicates that one platform is the initial or first-generation version from which another platform or subsequent generations are derived.
-
C.
targetDeviceGeneration
Indicates the specific hardware or model generation of the device that is the focus or recipient of an action or relationship.
-
D.
platformGenerationScope
Indicates the range or context within which a platform is created, applied, or considered valid.
-
E.
intendedReleasePlatform
Indicates the platform or medium for which something (such as a product, work, or content) is planned or designated to be released.
- 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_69f349b79f6c81909cb468c92c39c74d |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fed6da0390819096b88ef4714b144e |
completed | May 9, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69fed53517d081909966f31707625f1a |
completed | May 9, 2026, 6:33 a.m. |
Created at: May 1, 2026, 1:57 a.m.