Triple
T18806501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tranquillum House wellness resort |
E459888
|
entity |
| Predicate | mainGuestGroup |
P112711
|
FINISHED |
| Object | nine strangers |
—
|
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: nine strangers | Statement: [Tranquillum House wellness resort, mainGuestGroup, nine strangers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainGuestGroup Context triple: [Tranquillum House wellness resort, mainGuestGroup, nine strangers]
-
A.
primaryUserGroup
Indicates the main or default user group to which a user is primarily assigned or associated.
-
B.
primaryClientGroup
chosen
Indicates the main group of clients that an entity primarily serves or is chiefly associated with.
-
C.
mainForeignGroup
Indicates that an entity’s primary associated group or affiliation is a foreign (non-domestic) group.
-
D.
guestFlow
Indicates the movement or progression of guests through a space, process, or experience over time.
-
E.
guestRole
Indicates that one entity participates in or is associated with another entity in the capacity of a guest, specifying the nature or type of that guest participation.
- 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_69d8d398c7d4819091cb2f7e48948aeb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5a3d7f8d08190a3e02fab6dc40bb5 |
completed | April 20, 2026, 3:56 a.m. |
| PD | Predicate disambiguation | batch_69e48d1b10ec8190985c6fb5766ff981 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:53 a.m.