Triple
T26633828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atlantic Hotel Sail City |
E668575
|
entity |
| Predicate | hasConferenceFunction |
P95912
|
FINISHED |
| Object | regional conferences |
—
|
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: regional conferences | Statement: [Atlantic Hotel Sail City, hasConferenceFunction, regional conferences]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConferenceFunction Context triple: [Atlantic Hotel Sail City, hasConferenceFunction, regional conferences]
-
A.
hasConference
Indicates that an entity organizes, hosts, or is associated with a specific conference.
-
B.
hasConferenceType
chosen
Indicates that an entity is associated with or classified by a specific type or category of conference.
-
C.
hasConferenceSystem
Indicates that an entity is equipped with or utilizes a particular conference or conferencing system.
-
D.
hasConferenceSchedule
Indicates that an entity possesses or is associated with a defined schedule for a conference, detailing its planned sessions or events.
-
E.
hasConferenceCode
Indicates that a conference is associated with a specific identifying code.
- 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_69ee9d0024b8819090a7c8cf669a3b6c |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69fe08d2b2e48190ac7be6d62d4a44a3 |
completed | May 8, 2026, 4:01 p.m. |
| PD | Predicate disambiguation | batch_69fe06cd3af08190ae25de0dc0cdd573 |
completed | May 8, 2026, 3:52 p.m. |
Created at: April 27, 2026, 2:26 a.m.