Triple
T37563041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lochlamond, Renfrewshire |
E933876
|
entity |
| Predicate | hasNotableOwners |
P17607
|
FINISHED |
| Object | Dundonald family |
E2079156
|
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: Dundonald family | Statement: [Lochlamond, Renfrewshire, hasNotableOwners, Dundonald family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableOwners Context triple: [Lochlamond, Renfrewshire, hasNotableOwners, Dundonald family]
-
A.
hasNotableOwner
chosen
Indicates that an entity is or has been owned by a person or organization considered notable or significant.
-
B.
hasNotableHolders
Indicates that certain entities are recognized as prominent or distinguished bearers, owners, or occupants of another entity.
-
C.
hasNotableFounder
Indicates that an entity was founded or established by a person or organization considered especially significant or noteworthy.
-
D.
hasNotableMember
Indicates that a group, organization, or collection includes at least one member who is distinguished or noteworthy in some significant way.
-
E.
hasNotableNumber
Indicates that an entity is associated with a specific number that is considered significant, distinctive, or noteworthy in some context.
- F. None of above.
Provenance (4 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_69f76ecb4acc8190b53f96d0b013e415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40a7f00838819094bc0a201b28b1da |
completed | June 28, 2026, 4:49 a.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:17 p.m.