Triple
T29098718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Century Cycle |
E735080
|
entity |
| Predicate | lastPlayWritten |
P166315
|
FINISHED |
| Object | Radio Golf |
—
|
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: Radio Golf | Statement: [Century Cycle, lastPlayWritten, Radio Golf]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lastPlayWritten Context triple: [Century Cycle, lastPlayWritten, Radio Golf]
-
A.
laterWrittenIn
Indicates that one text or version was written at a later time than another, establishing a chronological order between the writings.
-
B.
laterPlayedWith
Indicates that one entity engaged in play with another entity at a later time than some referenced or implied earlier event.
-
C.
playedUntil
Indicates that an action or event involving playing continued up to a specific time, point, or condition.
-
D.
lastConcertoComposed
Indicates that one entity is the final (most recently) composed concerto in the body of work of another entity.
-
E.
laterWrittenDownAs
Indicates that something was recorded or documented in written form at a subsequent time after its original occurrence or expression.
- 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_69f05b0ed66481908f2e864fa550d2f1 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f6618344c08190a3c918a41a871381 |
completed | May 2, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f65c2376a08190be5215171e908e69 |
completed | May 2, 2026, 8:18 p.m. |
| PDg | Predicate description generation | batch_69f65f75ac608190a62cd6afce14f68e |
completed | May 2, 2026, 8:32 p.m. |
Created at: April 28, 2026, 11:10 a.m.