Triple
T25797467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bridget von Hammersmark |
E649725
|
entity |
| Predicate | meetsGroup |
P1139
|
FINISHED |
| Object | Inglourious Basterds |
—
|
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: Inglourious Basterds | Statement: [Bridget von Hammersmark, meetsGroup, Inglourious Basterds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: meetsGroup Context triple: [Bridget von Hammersmark, meetsGroup, Inglourious Basterds]
-
A.
meetsType
Indicates that one entity encounters or comes into contact with another entity in a particular manner or context.
-
B.
meetsEvery
Indicates that one entity encounters or comes into contact with every member of a specified set of entities.
-
C.
meetsTo
Indicates that one entity comes together with another at a specific time and place for an encounter, appointment, or interaction.
-
D.
meetsRegarding
Indicates that one entity meets with another specifically to discuss or address a particular topic, issue, or subject.
-
E.
meetsAs
chosen
Indicates that two entities encounter or come together at the same place and time, typically in a planned or recognized interaction.
- 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_69e7ab34f8c8819099f6c4dabdabf129 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f5ffc8635881909f3e05e3903f8d8c |
completed | May 2, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69f4938b960081909b53c074a3e0c7c2 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 22, 2026, 6:32 a.m.