Triple
T9237973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dangerous Minds |
E221983
|
entity |
| Predicate | mainCharacterBackground |
P39316
|
FINISHED |
| Object | former U.S. Marine |
—
|
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: former U.S. Marine | Statement: [Dangerous Minds, mainCharacterBackground, former U.S. Marine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainCharacterBackground Context triple: [Dangerous Minds, mainCharacterBackground, former U.S. Marine]
-
A.
protagonistBackground
Indicates that one entity serves as the background, history, or prior circumstances of the protagonist entity in a narrative or story.
-
B.
hasProtagonistBackground
chosen
Indicates that a work or narrative features a specified background or origin story for its main protagonist.
-
C.
inUniverseBackstory
Indicates that one entity provides narrative background or history for another within the fictional universe itself, as opposed to external or meta commentary.
-
D.
mainProtagonist
Indicates that the subject is the central character or primary focus in the narrative of the related work.
-
E.
characterOrigin
Indicates the source, background, or initial context from which a character originates.
- 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_69ca83ee26cc81909ac624e190597d6d |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccf09f9e908190801fe114c5e63984 |
completed | April 1, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_69cc7a4765648190aa9445c4a22dc471 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:30 p.m.