Triple
T35285177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MacLemmon |
E1019059
|
entity |
| Predicate | hasClanTerritorialAssociation |
P21614
|
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: [MacLemmon, hasClanTerritorialAssociation, Argyll]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClanTerritorialAssociation Context triple: [MacLemmon, hasClanTerritorialAssociation, Argyll]
-
A.
hasClanTerritory
Indicates that a clan possesses or controls a specific geographic territory as its domain.
-
B.
hasTerritorialAssociation
chosen
Indicates a relationship where an entity is linked or connected to a specific territory, area, or geographic region.
-
C.
associatedClan
Indicates a relationship where an entity is linked or belongs to a particular clan, group, or lineage.
-
D.
isPrincipalClanOf
Indicates that one clan holds primary or leading status over another clan within a hierarchical or organizational structure.
-
E.
associatedClanChief
Indicates a relationship where an entity is linked or connected to a particular clan chief, typically as the chief responsible for or representing that entity.
- 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_69fd783fed9c81909e792702636c4f1f |
completed | May 8, 2026, 5:44 a.m. |
| PD | Predicate disambiguation | batch_69fd7788e63c81909de22fdafcfe41c0 |
completed | May 8, 2026, 5:41 a.m. |
Created at: May 3, 2026, 4:03 p.m.