Triple
T6458987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Grindhouse |
E142066
|
entity |
| Predicate | associatedWithDefensiveIdentity |
P26731
|
FINISHED |
| Object | physical defense |
—
|
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: physical defense | Statement: [The Grindhouse, associatedWithDefensiveIdentity, physical defense]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithDefensiveIdentity Context triple: [The Grindhouse, associatedWithDefensiveIdentity, physical defense]
-
A.
associatedWithFlag
Indicates a relationship where an entity is linked or connected to a particular flag, such as a national, organizational, or symbolic banner.
-
B.
associatedWithMatch
Indicates a relationship where an entity is linked or connected to a particular match or matching event.
-
C.
defensiveReputation
chosen
Indicates that an entity is regarded or recognized as being strong, reliable, or skilled in defense.
-
D.
defendedAs
Indicates that one entity is presented, argued, or justified as being equivalent to or serving the role of another entity in a defensive or protective context.
-
E.
originallyAssociatedWith
Indicates that an entity was first linked, connected, or affiliated with another entity before any later changes in association.
- 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_69c008d2f91c8190a8178767a35e08fc |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c069f347f48190a2b22c5b648b17bd |
completed | March 22, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69c0673b44148190aed70084f0ff4992 |
completed | March 22, 2026, 10:03 p.m. |
Created at: March 22, 2026, 4:48 p.m.