Triple
T35076193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IC Lights series |
E1012313
|
entity |
| Predicate | intendedPlacement |
P124366
|
FINISHED |
| Object | table |
—
|
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: table | Statement: [IC Lights series, intendedPlacement, table]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedPlacement Context triple: [IC Lights series, intendedPlacement, table]
-
A.
canonicalPlacement
Indicates the standard or preferred position or arrangement of one entity relative to another within a defined structure or system.
-
B.
placementIn
Indicates that one entity is located or positioned within the spatial or structural bounds of another entity.
-
C.
designedToPlace
chosen
Indicates that something is intentionally created or configured for the purpose of positioning or setting another entity in a specific place or arrangement.
-
D.
placementType
Indicates the specific manner or category in which something is positioned, arranged, or assigned within a given context.
-
E.
decidedOverallPlacementOf
Indicates that one entity has determined or chosen the final ranking or positional order of another entity within a broader set or context.
- 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_69f76dd32c008190853aef6028f60208 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fdbc5ef46c8190bbcfb9798f4615b7 |
completed | May 8, 2026, 10:35 a.m. |
| PD | Predicate disambiguation | batch_69fdbb270338819082ce3f73903e884f |
completed | May 8, 2026, 10:29 a.m. |
Created at: May 3, 2026, 4:01 p.m.