Triple
T4136303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hope Lodge |
E85162
|
entity |
| Predicate | hasFacilityFeature |
P12416
|
FINISHED |
| Object | private or semi-private rooms |
—
|
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: private or semi-private rooms | Statement: [Hope Lodge, hasFacilityFeature, private or semi-private rooms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFacilityFeature Context triple: [Hope Lodge, hasFacilityFeature, private or semi-private rooms]
-
A.
hasFacilityType
Indicates that an entity possesses or is associated with a specific type or category of facility.
-
B.
hasFacilities
chosen
Indicates that an entity possesses, provides, or is equipped with certain facilities or physical resources.
-
C.
hasCampusFeature
Indicates that a campus possesses or includes a specific physical or functional feature.
-
D.
hasNotableFacility
Indicates that an entity possesses or hosts a facility that is of particular significance, prominence, or interest.
-
E.
hasCoreFacility
Indicates that an entity possesses, hosts, or is equipped with a central, shared facility that supports key operations or services.
- 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_69aed935ccd881909dc61f81bcdb7a78 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af03a0f3408190adba7a8513bd3d12 |
completed | March 9, 2026, 5:30 p.m. |
| PD | Predicate disambiguation | batch_69af018a54848190987f18c066c75068 |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:43 p.m.