Triple
T25189660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Envision Entertainment |
E630828
|
entity |
| Predicate | hasNotableWarFilm |
P26606
|
FINISHED |
| Object | Lone Survivor |
—
|
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: Lone Survivor | Statement: [Envision Entertainment, hasNotableWarFilm, Lone Survivor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableWarFilm Context triple: [Envision Entertainment, hasNotableWarFilm, Lone Survivor]
-
A.
hasNotableFilm
chosen
Indicates that an entity is associated with a film that is considered significant, well-known, or particularly noteworthy.
-
B.
hasNotableWar
Indicates that an entity is associated with a significant or historically important war.
-
C.
hasFictionalWar
Indicates that there exists a fictional or imagined war involving the related entities.
-
D.
hasNotableMilitaryFigure
Indicates that an entity is associated with or distinguished by a specific person recognized for significant military role, rank, or achievements.
-
E.
hasLiveActionFilm
Indicates that a subject has a corresponding live-action film adaptation or representation.
- 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_69e75a8a6d088190ba1e82a4345225e7 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f6c49627908190b3553474c7c3072b |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 21, 2026, 12:44 p.m.