Triple
T13672875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heavy |
E327794
|
entity |
| Predicate | hasProductionQuality |
P56662
|
FINISHED |
| Object | polished studio production |
—
|
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: polished studio production | Statement: [Heavy, hasProductionQuality, polished studio production]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProductionQuality Context triple: [Heavy, hasProductionQuality, polished studio production]
-
A.
hasQualityControl
Indicates that an entity is subject to processes or measures designed to monitor, verify, and maintain the quality of its outputs or operations.
-
B.
hasProductionValue
chosen
Indicates that something possesses or is associated with a particular level or type of production quality or cost.
-
C.
hasProduction
Indicates that an entity is associated with, or responsible for, the creation or manufacture of another entity or product.
-
D.
hasProductionStatus
Indicates the current stage or condition of an entity’s production process (e.g., planned, in progress, completed, or discontinued).
-
E.
isProductionReady
Indicates that something has met all necessary quality, stability, and performance criteria to be safely deployed and used in a live production environment.
- 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_69d8076f1fa8819094664a59b55010df |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc65aab348190a6611f5765f8392d |
completed | April 12, 2026, 4:20 p.m. |
| PD | Predicate disambiguation | batch_69dbbe8d8d0881908d6e89954f44eed4 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:53 p.m.