Triple
T37928600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lockout |
E946154
|
entity |
| Predicate | hasMapSize |
—
|
GENERATED |
| Object | small |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMapSize Context triple: [Lockout, hasMapSize, small]
-
A.
hasSize
chosen
Indicates that one entity possesses a particular physical magnitude or extent, such as length, volume, or overall dimensions.
-
B.
hasMapStructure
Indicates that one entity is organized or represented according to the structural layout or schema defined by another (map-like) entity.
-
C.
hasMapType
Indicates that one entity is associated with a specific type or category of map.
-
D.
hasMapLayout
Indicates that one entity possesses or is associated with a specific map configuration or spatial layout representation of another entity.
-
E.
hasMapRegion
Indicates that an entity is associated with, or belongs to, a specific geographic or logical map region.
- F. None of above.
Provenance (1 batch)
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_69f76ef3b7248190892fb9706423be7c |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:20 p.m.