Triple
T24869898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wonderworker |
E622389
|
entity |
| Predicate | typicalEpithetForm |
P175183
|
FINISHED |
| Object | “Name the Wonderworker” |
—
|
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: “Name the Wonderworker” | Statement: [Wonderworker, typicalEpithetForm, “Name the Wonderworker”]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalEpithetForm Context triple: [Wonderworker, typicalEpithetForm, “Name the Wonderworker”]
-
A.
languageOfEpithet
Indicates the language in which an epithet (such as a descriptive or honorary title) is expressed.
-
B.
epithetOrTitle
Indicates that one entity serves as an epithet, honorific, or formal title used to designate or characterize another entity.
-
C.
honorificEpitet
Indicates that one entity is referred to or addressed using an honorific epithet, expressing respect, status, or reverence toward that entity.
-
D.
hasMeaningOfEpithet
Indicates that one entity expresses or conveys the meaning or sense of another entity’s epithet.
-
E.
epithetAppliedBy
Indicates that a particular epithet or descriptive label is used or assigned by a specific agent to a target entity.
- 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_69e2fac3fdbc81909c2ec49be5743cd9 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f6cee547108190ad3bc84297d8f516 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
| PDg | Predicate description generation | batch_69f6cee3604c81908a07eade2f39064e |
completed | May 3, 2026, 4:28 a.m. |
Created at: April 18, 2026, 5:23 a.m.