Triple
T25005710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mr. Bobo |
E625835
|
entity |
| Predicate | warningMedium |
P157536
|
FINISHED |
| Object | jumping mice |
—
|
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: jumping mice | Statement: [Mr. Bobo, warningMedium, jumping mice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: warningMedium Context triple: [Mr. Bobo, warningMedium, jumping mice]
-
A.
warningType
Indicates the specific category or classification of a warning associated with an entity or event.
-
B.
dangerWarning
Indicates that one entity issues or represents a warning about potential danger associated with another entity or situation.
-
C.
warningContent
Indicates that one entity provides the specific message, text, or material that constitutes a warning directed toward another entity or audience.
-
D.
warningIssued
Indicates that a formal warning or alert has been communicated from one entity to another regarding a potential or existing risk, problem, or violation.
-
E.
warningGivenBy
Indicates that one entity issues or delivers a warning to another 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_69e2ff26c50481908bc82e799c9e6587 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f44b113f8c8190ae05102e9c2ae076 |
completed | May 1, 2026, 6:41 a.m. |
| PD | Predicate disambiguation | batch_69f442c0c2e88190acd7f170f10ccef6 |
completed | May 1, 2026, 6:05 a.m. |
| PDg | Predicate description generation | batch_69f448fe11f08190bdd53ca7ba2d51e4 |
completed | May 1, 2026, 6:32 a.m. |
Created at: April 18, 2026, 6:05 a.m.