Triple
T25206556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Dreamers |
E631267
|
entity |
| Predicate | historicalEventInPlot |
P2107
|
FINISHED |
| Object | May 1968 protests in France |
—
|
NE NERFINISHED |
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: May 1968 protests in France | Statement: [The Dreamers, historicalEventInPlot, May 1968 protests in France]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalEventInPlot Context triple: [The Dreamers, historicalEventInPlot, May 1968 protests in France]
-
A.
hasHistoricalEvent
chosen
Indicates that a historical event occurred in, is associated with, or is relevant to a particular entity.
-
B.
historicalEventsDescribed
Indicates that one entity (such as a document, text, or account) describes or recounts the historical events associated with another entity.
-
C.
historicalEventDescribedAs
Indicates that a historical event is characterized or portrayed using a particular description, label, or narrative.
-
D.
historicalNarrative
Indicates that one entity presents or constitutes a story or account about past events involving another entity.
-
E.
hasNearbyHistoricalEvent
Indicates that a given entity is located close to the site where a specific historical event occurred.
- 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_69e75a8b86c4819089eda22c843b739f |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 21, 2026, 12:52 p.m.