Triple
T6931506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Hotel |
E160444
|
entity |
| Predicate | hasPorchLength |
P73752
|
FINISHED |
| Object | approximately 660 feet |
—
|
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 660 feet | Statement: [Grand Hotel, hasPorchLength, approximately 660 feet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPorchLength Context triple: [Grand Hotel, hasPorchLength, approximately 660 feet]
-
A.
hasPorch
Indicates that one entity (typically a building or residence) includes or is equipped with a porch as part of its structure.
-
B.
hasPierLength
Indicates that one entity (typically a pier or similar structure) has a specified length measurement.
-
C.
hasCourtyardArea
Indicates that an entity includes or is associated with a courtyard and specifies the size or extent of that courtyard space.
-
D.
hasTerrace
Indicates that one entity includes, features, or is equipped with a terrace as part of its structure or property.
-
E.
hasBalcony
Indicates that a building or dwelling includes a balcony as part of its structure or features.
- 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_69c6884e15208190b9e91487eaafcf85 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6da3e58f08190857c14f538448039 |
completed | March 27, 2026, 7:27 p.m. |
| PD | Predicate disambiguation | batch_69c6d7bb577c81908ee8b415b4281f3d |
completed | March 27, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69c6d98625c88190a37fdf6d95d7fcbd |
completed | March 27, 2026, 7:24 p.m. |
Created at: March 27, 2026, 2:27 p.m.