Triple
T18779834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sharkey |
E459227
|
entity |
| Predicate | controls |
P760
|
FINISHED |
| Object | Bag End |
—
|
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: Bag End | Statement: [Sharkey, controls, Bag End]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bag End Context triple: [Sharkey, controls, Bag End]
-
A.
Bag End
chosen
Bag End is the cozy, well-furnished hobbit-hole in Hobbiton that serves as the ancestral home of the Baggins family in J.R.R. Tolkien’s Middle-earth.
-
B.
Stringbag
Stringbag was the affectionate nickname given to the British Fairey Swordfish biplane torpedo bomber, renowned for its outdated appearance yet remarkable effectiveness in World War II naval operations.
-
C.
BAG
BAG was the ICAO airline designator for Deutsche BA, a former German airline once affiliated with British Airways.
-
D.
BAG
BAG is the commonly used abbreviation for the Federal Labour Court of Germany, the country’s highest court for labor and employment law disputes.
-
E.
BAG
BAG is the German abbreviation for Switzerland’s Federal Office of Public Health, the national authority responsible for public health policy, disease prevention, and health regulation.
- 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_69d8d396f54c8190ba49db31e8743842 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5933e35a481908c21f7f488e1dd99 |
completed | April 20, 2026, 2:45 a.m. |
Created at: April 10, 2026, 11:52 a.m.