Triple
T28024074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AtlantaTrapScene |
E707761
|
entity |
| Predicate | sceneCharacteristic |
P61635
|
FINISHED |
| Object | producer-driven sound |
—
|
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: producer-driven sound | Statement: [AtlantaTrapScene, sceneCharacteristic, producer-driven sound]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sceneCharacteristic Context triple: [AtlantaTrapScene, sceneCharacteristic, producer-driven sound]
-
A.
sceneFeature
chosen
Indicates a characteristic, element, or attribute that is present within or helps define a particular scene.
-
B.
lightingCharacteristic
Indicates the specific qualities or properties of how something is lit, such as brightness, color, direction, or style of illumination.
-
C.
mediaCharacterization
Indicates how an entity is portrayed, described, or framed by media sources in terms of attributes, tone, or narrative.
-
D.
dataCharacteristic
Indicates that one entity specifies a property, attribute, or feature that characterizes a given piece of data.
-
E.
catalogCharacteristic
Indicates that a catalog has a specific characteristic or attribute associated with it.
- 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_69ef96baf3a881909a2b63844185dddd |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641def1e88190a05bf865ced78b23 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 8:11 p.m.