Triple
T31246656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | One After 909 |
E796702
|
entity |
| Predicate | reRecordedIn |
P171631
|
FINISHED |
| Object | 1969 |
—
|
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: 1969 | Statement: [One After 909, reRecordedIn, 1969]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reRecordedIn Context triple: [One After 909, reRecordedIn, 1969]
-
A.
wasRecordedIn
Indicates that an event, action, or piece of information was documented or captured within a specific record, medium, or recording session.
-
B.
recordedInText
Indicates that an event, fact, or relationship is documented or mentioned within a particular text or written source.
-
C.
oftenRecordedIn
Indicates that instances of one entity are frequently documented, logged, or captured within another entity (such as a medium, dataset, or record).
-
D.
reRecordedWith
Indicates that an existing recording was made again in collaboration with the specified entity (such as an artist, group, or producer).
-
E.
recordedForFilm
Indicates that an audio or performance was captured specifically for use in a film production.
- 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_69f224dc84d0819081f1cb6f9127e6b1 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6a1ac56b88190a820434b65c9fa23 |
completed | May 3, 2026, 1:15 a.m. |
| PD | Predicate disambiguation | batch_69f69fe463248190aa78128abeab1183 |
completed | May 3, 2026, 1:07 a.m. |
| PDg | Predicate description generation | batch_69f6a0e920cc8190a943fdd0594906c5 |
completed | May 3, 2026, 1:12 a.m. |
Created at: April 29, 2026, 9:11 p.m.