Triple
T25111175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Heart |
E628997
|
entity |
| Predicate | likelyProductionType |
P2475
|
FINISHED |
| Object | independent 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: independent production | Statement: [The Heart, likelyProductionType, independent production]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: likelyProductionType Context triple: [The Heart, likelyProductionType, independent production]
-
A.
eligibleProductionType
Indicates that a given entity qualifies for or is allowed to participate in a specified type or category of production.
-
B.
typicalProductionType
chosen
Indicates the usual or characteristic type of production activity associated with an entity.
-
C.
laterProductType
Indicates that one product type occurs or is introduced after another product type in time or sequence.
-
D.
usesProductionModel
Indicates that one entity employs or relies on another entity as its primary or official production model in practice.
-
E.
componentTypeProduced
Indicates that one entity produces or manufactures a specific type of component as an output of its activity or process.
- 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_69e2ff3169d08190973b6061d5009abd |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f465767c48819086fa0573dca12276 |
completed | May 1, 2026, 8:33 a.m. |
| PD | Predicate disambiguation | batch_69f44d8043b081908bbffd7f044b4f26 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 6:26 a.m.