Triple
T6953722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trekkers |
E161189
|
entity |
| Predicate | attend |
P2636
|
FINISHED |
| Object | Star Trek conventions |
—
|
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: Star Trek conventions | Statement: [Trekkers, attend, Star Trek conventions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attend Context triple: [Trekkers, attend, Star Trek conventions]
-
A.
attendance
chosen
Indicates the relationship between an event and the people who are present at or participate in that event.
-
B.
attendanceAnnounced
Indicates that an official statement has been made about whether and/or how many people will attend an event.
-
C.
laterAttends
Indicates that one entity attends an event or place at a time later than another referenced attendance.
-
D.
attendancePromotion
Indicates a relationship where one entity promotes, encourages, or incentivizes attendance at an event, activity, or location for another entity.
-
E.
appointedFor
Indicates that an entity has been officially assigned or designated to perform a specific role, task, or function for another entity or purpose.
- 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_69c68852a9a0819097797e31d492e273 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dacca12481908942ba793a104cc3 |
completed | March 27, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69c6d7bf0a7c8190b5ed4aca22ba9b97 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:29 p.m.