Triple
T31868614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barry Hawkins |
E813529
|
entity |
| Predicate | hasConsistentRecordAt |
P204118
|
FINISHED |
| Object | Crucible Theatre |
E97155
|
NE 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: Crucible Theatre | Statement: [Barry Hawkins, hasConsistentRecordAt, Crucible Theatre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConsistentRecordAt Context triple: [Barry Hawkins, hasConsistentRecordAt, Crucible Theatre]
-
A.
containsRecord
Indicates that one entity holds, includes, or stores a particular record within it.
-
B.
hasConsistency
Indicates that one entity maintains a stable, uniform, or coherent state, behavior, or set of properties in relation to another entity or over time.
-
C.
hasWorkRecordedThere
Indicates that a person or creator has had their work documented, produced, or otherwise officially recorded at a particular place or institution.
-
D.
hasWrittenRecordsIn
Indicates that an entity has produced or maintains written records in a specified medium, format, or location.
-
E.
hasCheckpoint
Indicates that an entity includes, contains, or is associated with one or more intermediate control or verification points within its structure, process, or path.
- F. None of above. chosen
Provenance (5 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_69f348ecb07481909c8f72619131b115 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a0326d40cb88190802f61fa832f8ca8 |
completed | May 12, 2026, 1:10 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2e65c0dd008190a14ea1be02d3f17c |
completed | June 14, 2026, 8:26 a.m. |
| PD | Predicate disambiguation | batch_6a03268b4f9c8190b3e135b37ed373c3 |
completed | May 12, 2026, 1:09 p.m. |
| PDg | Predicate description generation | batch_6a0326d30068819096da11fba14c2f31 |
completed | May 12, 2026, 1:10 p.m. |
Created at: April 30, 2026, 11:54 p.m.