Triple
T32068010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monsters, Inc. scare floor |
E818935
|
entity |
| Predicate | accessMethodToHumanWorld |
P5872
|
FINISHED |
| Object | closet doors |
—
|
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: closet doors | Statement: [Monsters, Inc. scare floor, accessMethodToHumanWorld, closet doors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessMethodToHumanWorld Context triple: [Monsters, Inc. scare floor, accessMethodToHumanWorld, closet doors]
-
A.
accessMethod
chosen
Indicates the means, process, or technique by which something is accessed, retrieved, or made available.
-
B.
accessDescribedAs
Indicates that the manner, conditions, or nature of access to something is characterized or specified by a particular description.
-
C.
humanAccessLevel
Indicates the level or degree of access or permissions granted to a human within a system or context.
-
D.
accessDirection
Indicates the direction or orientation from which access to something is obtained or permitted.
-
E.
accessMode
Indicates the manner or method by which an entity can be accessed, used, or interacted with.
- 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_69f739a638748190808e7a2930dce16e |
completed | May 3, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69f732f2dc6c8190a4e86da98cc5eb05 |
completed | May 3, 2026, 11:35 a.m. |
Created at: May 1, 2026, 12:22 a.m.