Triple
T35499516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UDIMET |
E1025959
|
entity |
| Predicate | industryStandardUse |
P8461
|
FINISHED |
| Object | jet 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: jet engines | Statement: [UDIMET, industryStandardUse, jet engines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: industryStandardUse Context triple: [UDIMET, industryStandardUse, jet engines]
-
A.
industryStandardFor
Indicates that something is widely accepted or recognized as the conventional or benchmark practice, specification, or norm within a particular industry.
-
B.
usedInIndustry
chosen
Indicates that something is employed or applied within a particular industry or industrial sector.
-
C.
standardsUsedIn
Indicates that certain standards are applied, referenced, or followed within a particular context, process, or entity.
-
D.
industryIntegrated
Indicates that something is closely connected or coordinated with industry practices, partners, or environments, often through collaboration, alignment, or direct involvement.
-
E.
industryStatus
Indicates the current operational or regulatory condition of an entity within its industry (e.g., active, inactive, regulated, or restricted status).
- 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_69f76dfc9c60819089c4217d93922615 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a225a77c81908f8953ccfeb14336 |
completed | May 3, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:04 p.m.