Triple
T7297952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colton Hall |
E164570
|
entity |
| Predicate | floorCountHistoricUse |
P27104
|
FINISHED |
| Object | upper floor used as convention hall |
—
|
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: upper floor used as convention hall | Statement: [Colton Hall, floorCountHistoricUse, upper floor used as convention hall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: floorCountHistoricUse Context triple: [Colton Hall, floorCountHistoricUse, upper floor used as convention hall]
-
A.
floorCount
Indicates the number of floors or levels that a building or structure has.
-
B.
residenceHistoric
Indicates that a residence has historical significance or is formally recognized as a historic dwelling.
-
C.
buildingUsedSince
Indicates that a particular building has been in use starting from a specified point in time.
-
D.
floorUseDistribution
chosen
Indicates how the use or function of space is distributed across different floors or levels within a structure.
-
E.
previousBuildingUse
Indicates that a building previously served a specified use or function before its current one.
- 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_69c6887a499881909dd23341399c59d8 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6eb8f83c881909e8eae85410f9659 |
completed | March 27, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69c6e76e67d88190bd3ca6864f45845a |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 3 p.m.