Triple
T31812324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marco Polo Tower |
E812039
|
entity |
| Predicate | hasBalconiesOn |
P187584
|
FINISHED |
| Object | all residential floors |
—
|
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: all residential floors | Statement: [Marco Polo Tower, hasBalconiesOn, all residential floors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBalconiesOn Context triple: [Marco Polo Tower, hasBalconiesOn, all residential floors]
-
A.
hasBalcony
Indicates that a building or dwelling includes a balcony as part of its structure or features.
-
B.
numberOfBalconies
Indicates the quantity of balconies associated with a given entity or property.
-
C.
hasBalconyOrTerrace
Indicates that an entity includes or is associated with a balcony or a terrace as part of its features.
-
D.
hasBalconyName
Indicates that an entity (such as a building or unit) has a balcony identified by a specific name.
-
E.
hasBalconyUse
Indicates that an entity makes use of or has access to a balcony for some purpose or activity.
- 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_69f348e846c081908eb468a0665afd55 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fb6fdc7eb081908ab8475efb38c430 |
completed | May 6, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69fb5a986e588190b7a10892bd2ff44c |
completed | May 6, 2026, 3:13 p.m. |
| PDg | Predicate description generation | batch_69fb6fdab95c81909acff3c6a2359787 |
completed | May 6, 2026, 4:44 p.m. |
Created at: April 30, 2026, 11:44 p.m.