Triple
T35285080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Limond |
E1019054
|
entity |
| Predicate | regionOfClanAllegiance |
P129330
|
FINISHED |
| Object | Argyll |
—
|
NE NERFINISHED |
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: Argyll | Statement: [Limond, regionOfClanAllegiance, Argyll]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionOfClanAllegiance Context triple: [Limond, regionOfClanAllegiance, Argyll]
-
A.
clanDistrict
chosen
Indicates that a clan is associated with, based in, or traditionally linked to a particular district.
-
B.
clanOrKingdom
Indicates a relationship where an entity is associated with, belongs to, or is part of a particular clan or kingdom.
-
C.
stateAllegiance
Indicates that one entity formally declares loyalty or support to another entity, such as a person, group, or state.
-
D.
namedForAllegiance
Indicates that an entity is named in reference to, or in honor of, a particular allegiance, affiliation, or loyalty.
-
E.
associatedClan
Indicates a relationship where an entity is linked or belongs to a particular clan, group, or lineage.
- F. None of above.
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_69f76de6d39c8190bb11342e4b91ff2b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ffbb1c5bf88190a0bf791213045885 |
completed | May 9, 2026, 10:54 p.m. |
| PD | Predicate disambiguation | batch_69ffba0ab0f881908f84ef81f7a1bfe8 |
completed | May 9, 2026, 10:49 p.m. |
Created at: May 3, 2026, 4:03 p.m.