Triple
T15035092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Innes Lloyd |
E378458
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Innes |
E582257
|
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: Innes | Statement: [Innes Lloyd, givenName, Innes]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Innes Context triple: [Innes Lloyd, givenName, Innes]
-
A.
Innes
chosen
Innes is a Scottish surname of Gaelic origin historically associated with families from the Moray region of northeast Scotland.
-
B.
McInness
McInness is a Scottish surname associated with Clan MacInnes, a Highland clan of ancient origin.
-
C.
Seatoller
Seatoller is a small hamlet in the Lake District of Cumbria, England, known as a gateway to the scenic Borrowdale valley and nearby mountain passes.
-
D.
Dugald
Dugald is a masculine given name of Scottish origin, historically associated with figures such as the philosopher Dugald Stewart.
-
E.
Craufurd
Craufurd is an alternative spelling of the surname Crawford, historically borne by several notable Scottish families and individuals.
- 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_69d85cd46b2c819090d054c27787f677 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded82b29948190acda49cbec3f927a |
completed | April 15, 2026, 12:13 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe9dddd0208190b2dac7a078de2931 |
completed | May 9, 2026, 2:37 a.m. |
Created at: April 10, 2026, 2:59 a.m.