Triple
T33498049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Le Dindon |
E857914
|
entity |
| Predicate | typicalProductionFeature |
P5084
|
FINISHED |
| Object | fast-paced staging |
—
|
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: fast-paced staging | Statement: [Le Dindon, typicalProductionFeature, fast-paced staging]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalProductionFeature Context triple: [Le Dindon, typicalProductionFeature, fast-paced staging]
-
A.
typicalProductionType
Indicates the usual or characteristic type of production activity associated with an entity.
-
B.
typicalFeatures
chosen
Indicates that the related entities are characteristic or commonly occurring features or attributes of something.
-
C.
typicalProducer
Indicates that an entity commonly or characteristically produces, creates, or manufactures another entity.
-
D.
productionFeature
Indicates that something is a characteristic, element, or attribute involved in the process or method of producing something.
-
E.
producerCharacteristic
Indicates a relationship where a producer is associated with a particular attribute, quality, or trait that characterizes them or their production.
- 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_69f3497660508190a541826a81f7e9ab |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f505c88190ac0879ab422c3054 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:38 a.m.