Triple
T6048186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tore |
E134719
|
entity |
| Predicate | hasShortForm |
P43
|
FINISHED |
| Object | Tor |
E142117
|
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: Tor | Statement: [Tore, hasShortForm, Tor]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tor Context triple: [Tore, hasShortForm, Tor]
-
A.
Tor
chosen
Tor is a masculine given name of Norse origin, commonly used in Scandinavian countries and derived from the name of the Norse thunder god Thor.
-
B.
Tor Tiv
Tor Tiv is the paramount traditional ruler and cultural leader of the Tiv people of central Nigeria.
-
C.
The Tor Project
The Tor Project is a nonprofit organization that develops and maintains privacy-focused tools—most notably the Tor anonymity network—to enable secure, uncensored communication online.
-
D.
TOR
TOR is the standard three-letter abbreviation used to represent the Toronto Maple Leafs in sports standings, statistics, and media.
-
E.
TOR
TOR is the official code designation used for the Georgian football club FC Torpedo Kutaisi.
- 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_69c00876a69881908088a2626d3b2666 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c056f387cc8190920b846995761aec |
completed | March 22, 2026, 8:54 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c113a65164819090883dbad3be5026 |
completed | March 23, 2026, 10:19 a.m. |
Created at: March 22, 2026, 4:09 p.m.