Triple
T32068018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monsters, Inc. scare floor |
E818935
|
entity |
| Predicate | hasShiftStructure |
P134317
|
FINISHED |
| Object | work shifts for scarers |
—
|
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: work shifts for scarers | Statement: [Monsters, Inc. scare floor, hasShiftStructure, work shifts for scarers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasShiftStructure Context triple: [Monsters, Inc. scare floor, hasShiftStructure, work shifts for scarers]
-
A.
hasDynamicShifts
Indicates that something exhibits changes or transitions in state, intensity, or behavior over time rather than remaining constant.
-
B.
hasShiftPressureFrom
Indicates that one entity experiences or is subjected to shift-related pressure originating from another entity.
-
C.
hasShiftRegister
Indicates that one entity includes, uses, or is associated with a shift register component or mechanism.
-
D.
haveStructure
chosen
Indicates that an entity possesses a particular internal organization, arrangement, or structural composition.
-
E.
hasNumberOfShifts
Indicates the quantity of work shifts associated with a given entity.
- 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_69f348fecc088190af1470afe5a969f0 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
Created at: May 1, 2026, 12:22 a.m.