Triple
T21555637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hymnen |
E531882
|
entity |
| Predicate | spatialFormat |
P91294
|
FINISHED |
| Object | quadraphonic |
—
|
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: quadraphonic | Statement: [Hymnen, spatialFormat, quadraphonic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spatialFormat Context triple: [Hymnen, spatialFormat, quadraphonic]
-
A.
cartographicFormat
Indicates the specific cartographic representation or format in which spatial or map-related information is expressed.
-
B.
spatialRepresentation
Indicates that one entity serves as a spatial depiction, model, or encoding of the location, layout, or geometric properties of another entity.
-
C.
spatialProperty
Indicates a relationship where one entity has a specific spatial characteristic, such as position, size, orientation, or geometric configuration in space, relative to a reference frame or other entities.
-
D.
storageFormat
chosen
Indicates the specific way in which data or content is physically or logically organized, encoded, and stored.
-
E.
spatialUnitType
Indicates the specific kind or category of spatial unit (e.g., parcel, building, region) that characterizes the spatial entity in question.
- 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_69e0c460232c81908de2c3819d17c00e |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eed2df48c88190894b6b08a5cb6390 |
completed | April 27, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69e6320766308190ba5dca2f7c826aa4 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:29 p.m.