Triple
T1987547
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Lorax (2012 film) |
E43174
|
entity |
| Predicate | MPAARatingReason |
P1959
|
FINISHED |
| Object | brief mild language |
—
|
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: brief mild language | Statement: [The Lorax (2012 film), MPAARatingReason, brief mild language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: MPAARatingReason Context triple: [The Lorax (2012 film), MPAARatingReason, brief mild language]
-
A.
mpaaRating
chosen
Indicates the official Motion Picture Association of America (MPAA) content rating assigned to a film or audiovisual work.
-
B.
statedReason
Indicates that one entity expresses or provides another entity as the explanation, justification, or motive for an action, event, or claim.
-
C.
USRating
Indicates that an entity has been assigned a rating, classification, or evaluation according to a United States–based standard or system.
-
D.
protectionReason
Indicates the justification or cause for which protection is provided or required in the relationship between entities.
-
E.
rating
Indicates an evaluation relationship where one entity assigns a qualitative or quantitative score or judgment to 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_69a88713ddc88190a969715658ebe7a8 |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb8ee02dc81908fec9fd8df7a4f40 |
completed | March 7, 2026, 5:34 a.m. |
| PD | Predicate disambiguation | batch_69abb79ad6888190be99943a9c73cf3e |
completed | March 7, 2026, 5:28 a.m. |
Created at: March 4, 2026, 7:37 p.m.