Triple
T21225378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Media Resource Function |
E523072
|
entity |
| Predicate | locatedInLayer |
P36580
|
FINISHED |
| Object | media layer |
—
|
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: media layer | Statement: [Media Resource Function, locatedInLayer, media layer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInLayer Context triple: [Media Resource Function, locatedInLayer, media layer]
-
A.
layerOf
chosen
Indicates that one entity forms a distinct layer or stratum of another entity within a structured or composite whole.
-
B.
locatedIn
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
-
C.
locatedOnLevel
Indicates that one entity is situated on a specific floor or level within a multi-level structure or system.
-
D.
sometimesLocatedIn
Indicates that an entity is located in a given place only at certain times or under certain conditions, rather than permanently or always.
-
E.
locatedUnder
Indicates that one entity is positioned directly or generally beneath another entity in space.
- 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_69e0b512ad94819087942b2ed925185f |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e734aa82c4819086cef6364619b4e9 |
completed | April 21, 2026, 8:26 a.m. |
| PD | Predicate disambiguation | batch_69e5f60e1a888190ba75e2e900270a4e |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:44 p.m.