Triple
T9836629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rio Bravo (1959 film) |
E239117
|
entity |
| Predicate | hasCharacter |
P2308
|
FINISHED |
| Object | Stumpy |
E286380
|
NE 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: Stumpy | Statement: [Rio Bravo (1959 film), hasCharacter, Stumpy]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Stumpy Context triple: [Rio Bravo (1959 film), hasCharacter, Stumpy]
-
A.
Stumpy
Stumpy is the elephant character that served as the official mascot of the 2011 ICC Cricket World Cup.
-
B.
Stumpy
chosen
Stumpy is a grizzled, limping old deputy known for his comic relief and fierce loyalty in the classic Western film "Rio Bravo."
-
C.
Stubby
Stubby is an internal remote procedure call (RPC) framework originally developed at Google that served as the precursor and design inspiration for gRPC.
-
D.
Tobo
Tobo is a small locality in eastern Sweden situated within Tierp Municipality in Uppsala County.
-
E.
Scruffy
Scruffy is the laconic, mustachioed janitor of Planet Express in the animated television series Futurama.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca84e314108190978324a4bdb959f8 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb33b07688190b78a70cf535c3efc |
completed | April 2, 2026, 12:07 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d1d5ccb28c8190a580767a57474557 |
completed | April 5, 2026, 3:23 a.m. |
Created at: March 30, 2026, 8:33 p.m.