Triple
T32139435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ASIC |
E820861
|
entity |
| Predicate | economicallyViableWhen |
P179262
|
FINISHED |
| Object | produced in high volume |
—
|
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: produced in high volume | Statement: [ASIC, economicallyViableWhen, produced in high volume]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: economicallyViableWhen Context triple: [ASIC, economicallyViableWhen, produced in high volume]
-
A.
hasEconomyCharacteristic
Indicates that an economy possesses a particular attribute, feature, or quality.
-
B.
hasEconomicDimension
Indicates that something involves, affects, or is characterized by economic factors, considerations, or consequences.
-
C.
hasEconomicDriver
Indicates that one entity serves as a primary source or cause of economic activity, growth, or value for another entity.
-
D.
hasEconomicLevel
Indicates that one entity possesses, is classified by, or is associated with a particular economic status or level.
-
E.
economyStatus
Indicates the current economic condition or level of prosperity associated with an entity, such as its financial health, growth, or stability.
- F. None of above. chosen
Provenance (4 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_69f349039e0c819091c7a7d322e3f46d |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7201e241c819092d56a7bb99dc94d |
completed | May 3, 2026, 10:14 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
| PDg | Predicate description generation | batch_69f71f8df5d48190944fbfbd9d573868 |
completed | May 3, 2026, 10:12 a.m. |
Created at: May 1, 2026, 12:30 a.m.