Triple
T4429761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Robin Hood films |
E95295
|
entity |
| Predicate | commonPlotElement |
P2762
|
FINISHED |
| Object | outlaw band in Sherwood Forest |
—
|
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: outlaw band in Sherwood Forest | Statement: [Robin Hood films, commonPlotElement, outlaw band in Sherwood Forest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonPlotElement Context triple: [Robin Hood films, commonPlotElement, outlaw band in Sherwood Forest]
-
A.
plotElement
chosen
Indicates that one entity functions as a narrative component or structural element within the storyline of another entity (such as a work of fiction or media).
-
B.
drivesPlotElement
Indicates that one element of the narrative is a primary cause or motivator for the development, progression, or outcome of another plot element.
-
C.
chartDepiction
Indicates that one entity is a chart that visually represents or depicts information about another entity.
-
D.
chartType
Indicates the specific kind or category of chart used to visually represent data in a given context.
-
E.
onChart
Indicates that one entity is visually represented or displayed on a chart associated with 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_69b3453c2a0c8190926b574c90766db9 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35569b3388190bdef2568f5dc04ce |
completed | March 13, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69b34f5eabe88190a12b244ea71e46d6 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:30 p.m.