Triple
T35004579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Galaxy Phase 2 |
E1009775
|
entity |
| Predicate | addsFacilityType |
P2836
|
FINISHED |
| Object | luxury hotel |
—
|
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: luxury hotel | Statement: [Galaxy Phase 2, addsFacilityType, luxury hotel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addsFacilityType Context triple: [Galaxy Phase 2, addsFacilityType, luxury hotel]
-
A.
hasFacilityType
chosen
Indicates that an entity possesses or is associated with a specific type or category of facility.
-
B.
modifiesFacility
Indicates a relationship where an entity changes, updates, or alters some aspect of a facility (such as its structure, function, or configuration).
-
C.
designedFacilityType
Indicates the type or category of facility that something (such as a plan, system, or component) is specifically designed for.
-
D.
namedFacilityType
Indicates that a facility is associated with or classified under a specific named type or category of facility.
-
E.
addsFeatureType
Indicates that one entity introduces or incorporates a specific feature type into another entity or system.
- 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_69f76dcb716881909f75e4fd60ab2284 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7858aa5508190a07dde993b3356fc |
completed | May 3, 2026, 5:27 p.m. |
| PD | Predicate disambiguation | batch_69f7841812f081909d878955d114088e |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.