Triple
T27619063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Compact Disc |
E700518
|
entity |
| Predicate | dataLayerLocation |
P162760
|
FINISHED |
| Object | beneath polycarbonate substrate |
—
|
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: beneath polycarbonate substrate | Statement: [Compact Disc, dataLayerLocation, beneath polycarbonate substrate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataLayerLocation Context triple: [Compact Disc, dataLayerLocation, beneath polycarbonate substrate]
-
A.
deploymentLocation
Indicates the place or environment where something (such as a system, resource, or component) is deployed or put into operational use.
-
B.
deltaLocation
Indicates a change or difference between two locations, typically specifying how one location has shifted relative to another.
-
C.
metadataLocation
Indicates the location or source where descriptive or administrative information about an entity is stored or can be accessed.
-
D.
documentLocation
Indicates the physical or digital place where a document is stored, kept, or can be accessed.
-
E.
locationOfCampaign
Indicates the place or geographic area where a particular campaign is conducted or based.
- 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_69ef6a4f1d9c8190b0705acda054368d |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f630dafea481909f5f59c5ed3269ee |
completed | May 2, 2026, 5:14 p.m. |
| PD | Predicate disambiguation | batch_69f62c1921008190a62675a31f66a875 |
completed | May 2, 2026, 4:53 p.m. |
| PDg | Predicate description generation | batch_69f62d14c24c81909e86678c1b5fd429 |
completed | May 2, 2026, 4:57 p.m. |
Created at: April 27, 2026, 2:13 p.m.