Triple
T34896333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caesar |
E1006444
|
entity |
| Predicate | warningPhrase |
P137717
|
FINISHED |
| Object | Beware the ides of March. |
—
|
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: Beware the ides of March. | Statement: [Caesar, warningPhrase, Beware the ides of March.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: warningPhrase Context triple: [Caesar, warningPhrase, Beware the ides of March.]
-
A.
warningType
Indicates the specific category or classification of a warning associated with an entity or event.
-
B.
warningSubject
Indicates that one entity is the topic or focus of a warning issued by another entity.
-
C.
warningContent
chosen
Indicates that one entity provides the specific message, text, or material that constitutes a warning directed toward another entity or audience.
-
D.
warningSigns
Indicates that one entity presents or serves as cautionary indications or alerts about potential danger, problems, or undesirable outcomes related to another entity.
-
E.
warningCall
Indicates that one entity initiates a call to another specifically to warn them about a danger, risk, or important cautionary information.
- 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_69f76dbfe5788190ad8b64f241f470c8 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f782c98fa08190870b68de2c1ff26a |
completed | May 3, 2026, 5:15 p.m. |
| PD | Predicate disambiguation | batch_69f781020cc4819088c40cb8589504e4 |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 3, 2026, 4 p.m.