Triple
T25722922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wye River Conference Centers |
E645038
|
entity |
| Predicate | hostedParticipant |
P2592
|
FINISHED |
| Object | United States mediation team |
—
|
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: United States mediation team | Statement: [Wye River Conference Centers, hostedParticipant, United States mediation team]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostedParticipant Context triple: [Wye River Conference Centers, hostedParticipant, United States mediation team]
-
A.
invitedParticipant
Indicates that an entity has been invited to take part in an event, activity, or interaction.
-
B.
host
chosen
Indicates that one entity provides space, resources, or services to accommodate, receive, or entertain another entity.
-
C.
eventParticipant
Indicates that an entity takes part in, is involved in, or participates in a particular event.
-
D.
guestHosted
Indicates that one entity temporarily hosted or presented an event, show, or program in place of or alongside the usual host.
-
E.
hostsParticipantsFrom
Indicates that an entity organizes or holds an event or activity that includes participants originating from another specified entity or location.
- 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_69e77e8476fc8190bd5e9d05b89fad0a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f60c3b09488190ade1b69ff7f0df0e |
completed | May 2, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f60b8461ac81908c5bd3d73eed59f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 21, 2026, 10:05 p.m.