Triple
T19138970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raw Materials |
E468503
|
entity |
| Predicate | perceptualStrategy |
P123106
|
FINISHED |
| Object | overlapping voices |
—
|
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: overlapping voices | Statement: [Raw Materials, perceptualStrategy, overlapping voices]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: perceptualStrategy Context triple: [Raw Materials, perceptualStrategy, overlapping voices]
-
A.
intendedPerception
Indicates that one entity is meant or designed to be perceived (e.g., seen, heard, or otherwise sensed) by another entity.
-
B.
viewOnPerception
Indicates a relationship where one entity expresses or embodies a particular stance, interpretation, or opinion about the nature or process of perception.
-
C.
visionAdaptation
Indicates how an entity’s visual system adjusts or responds to changes in lighting or visual conditions.
-
D.
perceivedMotion
Indicates that an entity experiences or detects the movement of another entity or object.
-
E.
sensoryModality
chosen
Indicates the type of sensory channel (e.g., visual, auditory, tactile) through which an experience, perception, or information is received or processed.
- 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_69d8dd0796a48190b34ce4cd9d3f3be5 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e3ef883c8190829138a560f2a3dc |
completed | April 20, 2026, 8:29 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b475d88190a8c15e8eb01dbfef |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:05 p.m.