Triple
T38196087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imperial Bowl |
E1005614
|
entity |
| Predicate | servedByLift |
P35396
|
FINISHED |
| Object | Imperial Express SuperChair |
—
|
NE NERFINISHED |
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: Imperial Express SuperChair | Statement: [Imperial Bowl, servedByLift, Imperial Express SuperChair]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedByLift Context triple: [Imperial Bowl, servedByLift, Imperial Express SuperChair]
-
A.
hasLift
chosen
Indicates that one entity is equipped with, contains, or provides access to a lift (elevator).
-
B.
lifts
Indicates that one entity raises or elevates another entity, typically by applying upward force or support.
-
C.
hasElevators
Indicates that one entity is equipped with or contains one or more elevators for vertical transportation.
-
D.
hasElevatorConnection
Indicates that there is a direct elevator-based connection or access route between two locations or entities.
-
E.
numberOfFloorsServed
Indicates the total count of distinct floors that are served or accessed by a given entity (such as an elevator or service system).
- 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_69f76dbd22f48190940318cea061e8bb |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a009d623f6c8190b702e2892c52fbb2 |
completed | May 10, 2026, 2:59 p.m. |
| PD | Predicate disambiguation | batch_6a009a3050d48190b64567f28e6ea463 |
completed | May 10, 2026, 2:46 p.m. |
Created at: May 3, 2026, 4:29 p.m.