Triple
T17158121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | James Williamson |
E416397
|
entity |
| Predicate | returnedToTheStooges |
P45021
|
FINISHED |
| Object | 2009 |
—
|
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: 2009 | Statement: [James Williamson, returnedToTheStooges, 2009]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: returnedToTheStooges Context triple: [James Williamson, returnedToTheStooges, 2009]
-
A.
returnsTo
chosen
Indicates that an entity goes back to a previous location, state, or entity it was associated with before.
-
B.
returnedFrom
Indicates that an entity has come back or been sent back from a specified source, location, or prior state.
-
C.
forcedToReturnTo
Indicates that one entity is compelled, against its preference or by external pressure or requirement, to go back to a previous place, state, or situation.
-
D.
returnedToTour
Indicates that an entity resumed or went back to participating in a tour after having left or paused it.
-
E.
returnedToTeam
Indicates that an individual who was previously away has come back to rejoin the same team.
- 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_69d886d279c081909f8ff1f743ddeb69 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f40d7ef08190a587c7c56f5c8569 |
completed | April 18, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69e3830d2a90819092386717dc56f0e8 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:37 a.m.