Triple
T6468882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of the Hotels |
E142296
|
entity |
| Predicate | frontName |
P45253
|
FINISHED |
| Object | Hotel front |
—
|
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: Hotel front | Statement: [Battle of the Hotels, frontName, Hotel front]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frontName Context triple: [Battle of the Hotels, frontName, Hotel front]
-
A.
frontType
Indicates the type or category of a front (e.g., boundary or leading side) that one entity presents or forms relative to another.
-
B.
front
Indicates that one entity is located directly before or facing another entity along a primary viewing or movement direction.
-
C.
frontPerson
Indicates that one entity serves as the primary representative, leader, or public face positioned at the forefront in relation to another entity.
-
D.
frontDesign
chosen
Indicates that one entity serves as the primary or visible front-facing design or appearance of another entity.
-
E.
frontOf
Indicates that one entity is positioned directly before another along a primary viewing or movement direction.
- 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_69c008d3bf4c8190bcf798c5ba9d6fb3 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06a16272c81909313455002cd884d |
completed | March 22, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69c0673d46a08190bc8bcd29f9555fe7 |
completed | March 22, 2026, 10:03 p.m. |
Created at: March 22, 2026, 4:49 p.m.