Triple
T32513005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Much Apu About Nothing |
E830984
|
entity |
| Predicate | basedOnTitleFrom |
P99044
|
FINISHED |
| Object | Much Ado About Nothing |
—
|
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: Much Ado About Nothing | Statement: [Much Apu About Nothing, basedOnTitleFrom, Much Ado About Nothing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedOnTitleFrom Context triple: [Much Apu About Nothing, basedOnTitleFrom, Much Ado About Nothing]
-
A.
titleBasedIn
Indicates that a creative work’s title is derived from, inspired by, or directly taken from a particular source or context.
-
B.
basedOnBy
Indicates that one entity is derived from, justified by, or constructed using another entity as its source, foundation, or reference.
-
C.
titleBasis
chosen
Indicates that one entity serves as the basis or source material for the title or name of another entity.
-
D.
hasTitleFrom
Indicates that one entity holds or uses a title that originates from, or is conferred by, another entity.
-
E.
basedOnName
Indicates that one entity is derived, determined, or identified using the name of 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_69f3492318348190ba37fb6b5f1d67f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe72dca2f08190beff17de3d2aada6 |
completed | May 8, 2026, 11:33 p.m. |
| PD | Predicate disambiguation | batch_69fe70bca8d08190b810e1e616ceac44 |
completed | May 8, 2026, 11:24 p.m. |
Created at: May 1, 2026, 1 a.m.