Triple
T29066264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tenderness |
E735681
|
entity |
| Predicate | revisitsEarlierMaterialOf |
P162502
|
FINISHED |
| Object | Al Jarreau |
—
|
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: Al Jarreau | Statement: [Tenderness, revisitsEarlierMaterialOf, Al Jarreau]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: revisitsEarlierMaterialOf Context triple: [Tenderness, revisitsEarlierMaterialOf, Al Jarreau]
-
A.
revisitsThemeOf
chosen
Indicates that one work, section, or passage returns to and further explores a theme that was previously introduced elsewhere.
-
B.
earlierOralMaterialFrom
Indicates that the subject is derived from or based on earlier oral material provided by the object.
-
C.
reappearsIn
Indicates that an entity that previously appeared becomes present or visible again in the same or another context.
-
D.
reusedIn
Indicates that something previously used in one context or instance is used again in another context or instance.
-
E.
reintroduced
Indicates that an entity that was previously removed, extinct, or absent has been brought back or restored to a place, context, or state.
- 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_69f077e85498819088b65186550da8cd |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6617ba4a88190bfc5c305acb4f93f |
completed | May 2, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f660f082508190a95a7888ad66cb2e |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 10:18 a.m.