Triple
T4629365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 7 World Trade Center |
E101173
|
entity |
| Predicate | hasNumberOfElevators |
P1274
|
FINISHED |
| Object | approximately 30 |
—
|
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: approximately 30 | Statement: [7 World Trade Center, hasNumberOfElevators, approximately 30]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumberOfElevators Context triple: [7 World Trade Center, hasNumberOfElevators, approximately 30]
-
A.
numberOfElevators
chosen
Indicates the total count of elevators associated with a given entity or location.
-
B.
hasElevators
Indicates that one entity is equipped with or contains one or more elevators for vertical transportation.
-
C.
hasNumberOfElevatorBanks
Indicates the relationship specifying how many distinct elevator banks are present in or associated with a given entity.
-
D.
hasEscalators
Indicates that one entity is equipped with or contains escalators that can be used for movement between different levels or areas.
-
E.
hasHighSpeedElevators
Indicates that a building or structure is equipped with elevators capable of operating at high speeds.
- 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_69bd43d0497c8190ac23c65c5804846a |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5a300e6081909fa9f504aada33ea |
completed | March 20, 2026, 2:31 p.m. |
| PD | Predicate disambiguation | batch_69bd5233cb5081908807e2b150f0ca06 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:13 p.m.