Triple
T7150389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | materials engineering |
E166676
|
entity |
| Predicate | appliedInIndustry |
P8461
|
FINISHED |
| Object | electronics industry |
—
|
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: electronics industry | Statement: [materials engineering, appliedInIndustry, electronics industry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliedInIndustry Context triple: [materials engineering, appliedInIndustry, electronics industry]
-
A.
usedInIndustry
chosen
Indicates that something is employed or applied within a particular industry or industrial sector.
-
B.
containsIndustry
Indicates that one entity includes or encompasses a particular industry within its scope, structure, or operations.
-
C.
isPartOfIndustry
Indicates that one entity belongs to, operates within, or is categorized under a particular industry sector.
-
D.
industrialCategory
Indicates the industry or sector classification to which an entity (such as a business or organization) belongs.
-
E.
operatorIndustry
Indicates that an operator (such as a company or organization) is engaged in or associated with a particular industry sector.
- 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_69c68886779c8190a8e3fbabffe68253 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e7f28b188190b1732ca711666531 |
completed | March 27, 2026, 8:26 p.m. |
| PD | Predicate disambiguation | batch_69c6e1caf4e48190b47bb398a3c1554d |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:46 p.m.