Triple
T16685176
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holly Aird |
E405443
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Aird |
E903750
|
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: Aird | Statement: [Holly Aird, familyName, Aird]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Aird Context triple: [Holly Aird, familyName, Aird]
-
A.
Aird
chosen
Aird is a historic district in the Scottish Highlands traditionally associated with Clan Fraser.
-
B.
Airegin
Airegin is a celebrated jazz composition by saxophonist Sonny Rollins, known as a bebop standard frequently performed and recorded by leading jazz musicians.
-
C.
Aire
Aire is a river in northern France that flows through the Grand Est region and is a tributary of the Aisne River.
-
D.
Aire
Aire is a given name that can be used for individuals of any gender, often chosen for its airy, nature-inspired sound and uniqueness.
-
E.
Airlie
Airlie is a historic Scottish Highland war cry associated with Clan Ogilvy, invoking the clan’s ancestral seat and martial heritage.
- 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_69d8838c28748190b3f5967c743940ab |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37ea550c0819085bd36c44237a61a |
completed | April 18, 2026, 12:52 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a008a43f6a08190913ca123a2377f95 |
completed | May 10, 2026, 1:38 p.m. |
Created at: April 10, 2026, 5:19 a.m.