Triple
T35285179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MacLemmon |
E1019059
|
entity |
| Predicate | isPartOfClanSystem |
P200090
|
FINISHED |
| Object | Scottish clan system |
—
|
LITERAL 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: Scottish clan system | Statement: [MacLemmon, isPartOfClanSystem, Scottish clan system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfClanSystem Context triple: [MacLemmon, isPartOfClanSystem, Scottish clan system]
-
A.
isPrincipalClanOf
Indicates that one clan holds primary or leading status over another clan within a hierarchical or organizational structure.
-
B.
clanSystem
Indicates a social structure in which individuals are organized into kin-based groups (clans) that define relationships, obligations, and affiliations among them.
-
C.
hasClanStatus
Indicates that an entity holds a specific role, rank, or membership status within a clan or clan-like group.
-
D.
hasClanOrBandStructure
Indicates that an entity is organized into, or participates in, a social structure based on clans or bands.
-
E.
hasMemberClan
chosen
Indicates that a group or organization includes a specific clan as one of its members.
- 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_69ff90b673248190b4dda9e005642d17 |
completed | May 9, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69ff8d5bee1081909274052945e98a6f |
completed | May 9, 2026, 7:39 p.m. |
Created at: May 3, 2026, 4:03 p.m.