Triple
T22884259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dirk Blocker |
E567559
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Blocker |
—
|
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: Blocker | Statement: [Dirk Blocker, familyName, Blocker]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Blocker Context triple: [Dirk Blocker, familyName, Blocker]
-
A.
Blocker
chosen
Blocker is a surname most notably associated with American actors Dan Blocker and his son Dirk Blocker.
-
B.
Blockers
Blockers is a 2018 American comedy film about overprotective parents trying to stop their daughters’ prom-night sex pact.
-
C.
Blok
Blok is a Russian surname most famously borne by the Symbolist poet Alexander Blok.
-
D.
Blockblister
Blockblister is a recurring parody sketch on The Amanda Show that spoofs the Blockbuster video rental chain with an overzealous family-run store.
-
E.
Blok-L
Blok-L is a Soviet-era rocket upper stage used primarily to place payloads into highly elliptical orbits, notably for Molniya communications satellites.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e2458a92ec81908fc1cd5f6407d2ab |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17fbfc5848190aa612ea51df5a9ec |
completed | April 29, 2026, 3:49 a.m. |
Created at: April 17, 2026, 3:40 p.m.