Triple
T6602164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tamsin Wise |
E149024
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Wise |
E118203
|
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: Wise | Statement: [Tamsin Wise, familyName, Wise]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wise Context triple: [Tamsin Wise, familyName, Wise]
-
A.
Wise
chosen
Wise is a surname shared by various notable individuals across fields such as entertainment, politics, and academia.
-
B.
Wise
Wise is a London-based financial technology company best known for its low-cost international money transfer and multi-currency account services.
-
C.
the Wise
The Wise is the honorific epithet of Frederick III, Elector of Saxony, renowned for protecting Martin Luther and playing a key role in the early Reformation.
-
D.
the Wise
"The Wise" is an honorific epithet denoting Yaroslav I of Kyiv’s reputation for wisdom and effective rule as a medieval Grand Prince of Kievan Rus'.
-
E.
Wisen
Wisen is a small municipality in the canton of Solothurn in Switzerland, situated in a rural, hilly region near the border with the canton of Basel-Landschaft.
- 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_69c687eaa7508190bb58ce2aa02039b3 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6af10303081909541a140f8898979 |
completed | March 27, 2026, 4:23 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c6e434afd08190807faf0069c70cce |
completed | March 27, 2026, 8:10 p.m. |
Created at: March 27, 2026, 1:56 p.m.