Triple
T21456863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baz |
E529363
|
entity |
| Predicate | associatedWithKeepingRole |
P144417
|
FINISHED |
| Object | wicket-keeper |
—
|
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: wicket-keeper | Statement: [Baz, associatedWithKeepingRole, wicket-keeper]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithKeepingRole Context triple: [Baz, associatedWithKeepingRole, wicket-keeper]
-
A.
associatedWithTitleHolderRole
Indicates a relationship where an entity is connected to, or linked with, a role held by a title holder.
-
B.
associatedWithUnitRole
Indicates that an entity has a connection or linkage to a specific role within a particular unit or organizational subdivision.
-
C.
associatedWithRoleOfNameBearer
Indicates that an entity is connected to or involved with the specific role or function held by a designated name bearer.
-
D.
roleWith
Indicates that one entity holds or performs a particular role in relation to another entity.
-
E.
associatedWithRule
Indicates that an entity is linked or connected to a specific rule, such as being governed, constrained, or defined by that rule.
- 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_69e0c458133481908ae8b41a12c4edec |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9e9d7af248190a3bc06a390f390bf |
completed | April 23, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_69e631df1b38819088d3604854e697b4 |
completed | April 20, 2026, 2:02 p.m. |
| PDg | Predicate description generation | batch_69e63d2aca38819094d312078feaa436 |
completed | April 20, 2026, 2:50 p.m. |
Created at: April 16, 2026, 6:08 p.m.