Triple
T31200735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Lange |
E795467
|
entity |
| Predicate | coverCreditName |
P147478
|
FINISHED |
| Object | John Lange |
—
|
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: John Lange | Statement: [John Lange, coverCreditName, John Lange]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coverCreditName Context triple: [John Lange, coverCreditName, John Lange]
-
A.
includesCreditTo
chosen
Indicates that one entity explicitly acknowledges or attributes credit to another entity, typically for contribution, authorship, or source.
-
B.
coverComposer
Indicates that one entity is the composer of the music for another entity that is a cover version of a work.
-
C.
coversLabel
Indicates that one entity’s scope, content, or applicability includes or encompasses the label associated with another entity.
-
D.
coverSymbol
Indicates that one symbol or notation is used as a cover or representative marker for another entity in a given context.
-
E.
coverRole
Indicates that one entity temporarily assumes or fills the role, duties, or position normally held by another entity.
- 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_69f224d8c6608190b7882466521f62be |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
Created at: April 29, 2026, 9:09 p.m.