Triple
T29692055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Dodge Twins |
E751234
|
entity |
| Predicate | typicalPerformanceElements |
P203851
|
FINISHED |
| Object | singing |
—
|
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: singing | Statement: [The Dodge Twins, typicalPerformanceElements, singing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPerformanceElements Context triple: [The Dodge Twins, typicalPerformanceElements, singing]
-
A.
typicalPerformanceFor
Indicates the usual or characteristic level of performance associated with a given entity, context, or condition.
-
B.
typicalPerformance
Indicates the usual or characteristic level at which an entity performs under normal conditions.
-
C.
typicalPerformanceForces
Indicates the forces that are normally or characteristically exerted or experienced during a given type of performance or operation.
-
D.
typicalPerformers
Indicates the entities that most commonly or characteristically perform a given action or role.
-
E.
typicalPerformanceSetting
Indicates the usual or most common context, venue, or environment in which a performance or activity typically takes place.
- 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_69f0d625b09481909b0b69aea1e846c8 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a0224f4b6cc8190a8f79700a9af765f |
completed | May 11, 2026, 6:50 p.m. |
| PD | Predicate disambiguation | batch_6a0223f01eb081909419518fdd45f2a4 |
completed | May 11, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_6a0224f3a02481908799158630d2f430 |
completed | May 11, 2026, 6:50 p.m. |
Created at: April 28, 2026, 7:17 p.m.