Triple
T20343740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Woe oracles |
E495810
|
entity |
| Predicate | haveTypicalIntroductoryWord |
P30529
|
FINISHED |
| Object | woe |
—
|
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: woe | Statement: [Woe oracles, haveTypicalIntroductoryWord, woe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: haveTypicalIntroductoryWord Context triple: [Woe oracles, haveTypicalIntroductoryWord, woe]
-
A.
hasIntro
Indicates that an entity includes or is associated with an introductory section or opening part.
-
B.
hasIntroduction
Indicates that one entity includes or provides an introductory section, part, or presentation for another entity.
-
C.
hasSpokenWordIntro
Indicates that an entity includes or features an introductory segment performed in spoken word form.
-
D.
hasTypicalSubject
chosen
Indicates that something is commonly or characteristically used as the subject (agent or topic) of a given relation or action.
-
E.
introduced
Indicates that one entity caused another entity to become known, presented, or brought into use for the first time to a person, group, or context.
- 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_69e0b4a3320881909495ae8bc30bc2dc |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e67837bef8819091e552d1c8a1665c |
completed | April 20, 2026, 7:02 p.m. |
| PD | Predicate disambiguation | batch_69e57636b4808190bc2855af48a3ccdc |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:24 a.m.