Triple
T9683525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nick Laird |
E234346
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Laird |
E729060
|
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: Laird | Statement: [Nick Laird, familyName, Laird]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Laird Context triple: [Nick Laird, familyName, Laird]
-
A.
Laird
chosen
Laird is a given name of Scottish origin traditionally used as a masculine middle or first name, associated with landownership and nobility.
-
B.
Dugald
Dugald is a masculine given name of Scottish origin, historically associated with figures such as the philosopher Dugald Stewart.
-
C.
Lawrie
Lawrie is the middle name of Wilfred Lawrie Nicholas Johnson, the son of former UK Prime Minister Boris Johnson and Carrie Johnson.
-
D.
Archibold
Archibold is a less common variant spelling of the given name Archibald, traditionally of Germanic and Scottish origin.
-
E.
Shriever
Shriever is a surname, a variant spelling of "Shriver," borne by various individuals of English-speaking origin.
- 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_69ca84c99e34819092e5563a7106cfca |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9ccf21a08190a1302b933b9e50be |
completed | April 1, 2026, 10:31 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d1910192e88190b10409ae62c1c948 |
completed | April 4, 2026, 10:30 p.m. |
Created at: March 30, 2026, 8:16 p.m.