Triple
T23321206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | In My Eyes |
E591153
|
entity |
| Predicate | sceneOrigin |
P54187
|
FINISHED |
| Object | Washington, D.C. hardcore scene |
—
|
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: Washington, D.C. hardcore scene | Statement: [In My Eyes, sceneOrigin, Washington, D.C. hardcore scene]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sceneOrigin Context triple: [In My Eyes, sceneOrigin, Washington, D.C. hardcore scene]
-
A.
sceneCenter
Indicates that one entity serves as the central or focal point of a scene in relation to another entity.
-
B.
coordinateOrigin
Indicates the reference point in space from which a coordinate system’s positions or measurements are defined.
-
C.
centerOfOrigin
chosen
Indicates the place or region where something (such as a species, product, idea, or movement) originally began or was first developed.
-
D.
sceneFeature
Indicates a characteristic, element, or attribute that is present within or helps define a particular scene.
-
E.
depthOrigin
Indicates the reference point or source location from which the depth of an object or region is measured.
- 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_69e25d1effe4819096907f95f610dbff |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f19785ae5481908816b37da95ceb3e |
completed | April 29, 2026, 5:30 a.m. |
| PD | Predicate disambiguation | batch_69effcf8ca2c8190887d4f4656617d21 |
completed | April 28, 2026, 12:19 a.m. |
Created at: April 17, 2026, 5:07 p.m.