Triple
T27412180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alexander Morozov |
E692181
|
entity |
| Predicate | inIndustry |
P67916
|
FINISHED |
| Object | defense 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: defense industry | Statement: [Alexander Morozov, inIndustry, defense industry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inIndustry Context triple: [Alexander Morozov, inIndustry, defense industry]
-
A.
containsIndustry
Indicates that one entity includes or encompasses a particular industry within its scope, structure, or operations.
-
B.
operatorIndustry
chosen
Indicates that an operator (such as a company or organization) is engaged in or associated with a particular industry sector.
-
C.
industryContext
Indicates the industry or sector within which an entity, activity, or relationship is situated or most relevant.
-
D.
peakIndustry
Indicates that an entity is at the highest or most dominant level within a particular industry or sector.
-
E.
industryIntegrated
Indicates that something is closely connected or coordinated with industry practices, partners, or environments, often through collaboration, alignment, or direct involvement.
- 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_69ef5205fc808190ad3efc5525b8e6d6 |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f62cdb62608190a8e1c84a631de5ce |
completed | May 2, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69f623aaf40081909f947431424a1d55 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 12:32 p.m.