Triple
T16553865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lafayette Towers Apartments East |
E402140
|
entity |
| Predicate | hasCorridorLayout |
P26881
|
FINISHED |
| Object | double-loaded corridors |
—
|
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: double-loaded corridors | Statement: [Lafayette Towers Apartments East, hasCorridorLayout, double-loaded corridors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCorridorLayout Context triple: [Lafayette Towers Apartments East, hasCorridorLayout, double-loaded corridors]
-
A.
hasCorridor
Indicates that one entity includes, is connected by, or provides access through a corridor to another entity.
-
B.
hasCorridorName
Indicates that an entity is associated with or identified by the name of a specific corridor.
-
C.
corridorType
chosen
Indicates the specific kind or classification of a corridor associated with an entity or location.
-
D.
isPartOfCorridorSystem
Indicates that one entity forms a component or segment within a larger interconnected corridor system.
-
E.
corridorOrientation
Indicates the directional alignment or bearing of a corridor relative to a reference frame or coordinate 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_69d88384bc30819084229e7dcdc39a41 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e34fc737ac8190b755e2a39b6ef32b |
completed | April 18, 2026, 9:32 a.m. |
| PD | Predicate disambiguation | batch_69e296a47b7481909d9958158510c806 |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:15 a.m.