Triple
T21124194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Loose Box |
E520510
|
entity |
| Predicate | hasPhysicalLocationWithin |
P57262
|
FINISHED |
| Object | Electric Light |
—
|
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: Electric Light | Statement: [The Loose Box, hasPhysicalLocationWithin, Electric Light]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPhysicalLocationWithin Context triple: [The Loose Box, hasPhysicalLocationWithin, Electric Light]
-
A.
hasPhysicalLocationType
Indicates that an entity is associated with a specific kind or category of physical location (e.g., building type, facility type, or place type).
-
B.
isPhysicalLocation
Indicates that one entity serves as a physical, real-world place or site associated with another entity.
-
C.
hasLocationRole
Indicates that an entity holds or plays a specific role in relation to a particular location (e.g., origin, destination, storage site, or operational area).
-
D.
existsWithin
chosen
Indicates that one entity is located inside the spatial, temporal, or conceptual boundaries of another entity.
-
E.
likelyLocatedIn
Indicates that an entity is probably situated within or associated with a particular location, though not with absolute certainty.
- 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_69e0b50a623881909c0bbaf4f2c055e7 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e72237c1a4819090987c645114d452 |
completed | April 21, 2026, 7:07 a.m. |
| PD | Predicate disambiguation | batch_69e5f5ed6c8c8190b31092a5d4c3de5d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 2:56 p.m.