Triple
T37648566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | C-123 Provider |
E937106
|
entity |
| Predicate | laterVariantEngineType |
P108970
|
FINISHED |
| Object | turboprop engines |
—
|
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: turboprop engines | Statement: [C-123 Provider, laterVariantEngineType, turboprop engines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterVariantEngineType Context triple: [C-123 Provider, laterVariantEngineType, turboprop engines]
-
A.
extendedVariantUsedFor
Indicates that one entity is an extended or modified variant that is used in place of, or for the purposes of, another entity.
-
B.
laterVariantRole
Indicates that one role is a subsequent or later variant of another, reflecting a modified or evolved version of the original role.
-
C.
exportVariantOf
Indicates that one entity is an exported version or externally released form derived from another, original entity.
-
D.
developmentVariant
chosen
Indicates that one entity is a variant or alternative form of another in the context of development (e.g., a different developmental version, configuration, or pathway).
-
E.
laterVersion
Indicates that one entity is a subsequent or more recent version of another entity in a version sequence.
- 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_69f76ed4fe908190b8061c5c135e0971 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a012efebda88190a90c8f650e4b1ee9 |
completed | May 11, 2026, 1:21 a.m. |
| PD | Predicate disambiguation | batch_6a01298cc604819087c836659c128926 |
completed | May 11, 2026, 12:57 a.m. |
Created at: May 3, 2026, 4:18 p.m.