Triple
T2953335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First National Bank building (Tampico) |
E79871
|
entity |
| Predicate | hasUpperFloorUse |
P44317
|
FINISHED |
| Object | residential apartment |
—
|
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: residential apartment | Statement: [First National Bank building (Tampico), hasUpperFloorUse, residential apartment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUpperFloorUse Context triple: [First National Bank building (Tampico), hasUpperFloorUse, residential apartment]
-
A.
hasUpperFloor
Indicates that one entity possesses or includes an upper floor relative to another level or reference point.
-
B.
hasLowerFloor
Indicates that one location, structure, or level includes or is directly connected to a floor situated below another floor.
-
C.
hasTopFloorFeature
Indicates that a building’s top floor possesses a specific feature, attribute, or amenity.
-
D.
hasFloor
Indicates that one entity possesses, includes, or is associated with a particular floor or level within a structure.
-
E.
hasBasementUse
Indicates that a building or structure’s basement is used for a specified purpose or function.
- F. None of above. chosen
Provenance (4 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_69ad8b1276588190a374a0b12e0f7bdf |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad98fe4b688190a0f68c4f80cd6f8f |
completed | March 8, 2026, 3:42 p.m. |
| PD | Predicate disambiguation | batch_69ad960a70ac8190816b5ae3e8631031 |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97f5d28c8190899d90204dc43428 |
completed | March 8, 2026, 3:38 p.m. |
Created at: March 8, 2026, 2:57 p.m.