Triple
T30956431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wenlock Olympian Society |
E788688
|
entity |
| Predicate | hasOrganised |
P193130
|
FINISHED |
| Object | Wenlock Olympian Games |
—
|
NE NERFINISHED |
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: Wenlock Olympian Games | Statement: [Wenlock Olympian Society, hasOrganised, Wenlock Olympian Games]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOrganised Context triple: [Wenlock Olympian Society, hasOrganised, Wenlock Olympian Games]
-
A.
alsoOrganized
Indicates that the same entity was additionally responsible for organizing another related event, activity, or entity.
-
B.
organisedWith
Indicates that two or more entities are arranged, coordinated, or structured together as part of the same organizing context or effort.
-
C.
organisedFor
Indicates that something has been arranged, structured, or coordinated specifically to serve, support, or benefit a particular entity or purpose.
-
D.
organizedAt
Indicates that an event or activity was arranged, planned, or hosted at a specific location or venue.
-
E.
organisedSince
Indicates that an entity has been formally organized or established starting from a specified point in time.
- F. None of above. chosen
Provenance (4 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_69f224c28c1881908c33b45d689f1724 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd389cb28c819099a77e28d25f258a |
completed | May 8, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69fd3826d8048190ada79a5868d1d7f3 |
completed | May 8, 2026, 1:11 a.m. |
| PDg | Predicate description generation | batch_69fd389b653c81908a97ab2eff98c6ea |
completed | May 8, 2026, 1:12 a.m. |
Created at: April 29, 2026, 8:54 p.m.