Triple
T32068011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monsters, Inc. scare floor |
E818935
|
entity |
| Predicate | doorTransportSystem |
P1379
|
FINISHED |
| Object | overhead rail system |
—
|
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: overhead rail system | Statement: [Monsters, Inc. scare floor, doorTransportSystem, overhead rail system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: doorTransportSystem Context triple: [Monsters, Inc. scare floor, doorTransportSystem, overhead rail system]
-
A.
transports
Indicates that one entity carries or conveys another entity from one place to another.
-
B.
transportType
chosen
Indicates the mode or means of transportation used in carrying something or someone from one place to another.
-
C.
transportationFunction
Indicates that one entity serves to move or carry another entity from one place to another.
-
D.
roadTransportFunction
Indicates a functional relationship in which something serves or is used for the transport of people or goods via roads.
-
E.
transportDevelopment
Indicates the development or improvement of transportation systems, infrastructure, or services connecting places or entities.
- 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_69f6b52037948190b7928563c1d9b20d |
completed | May 3, 2026, 2:38 a.m. |
| PD | Predicate disambiguation | batch_69f6b154b3dc819087115f5f63f7b00f |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:22 a.m.