Triple
T12146043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clan MacNab |
E289323
|
entity |
| Predicate | clanSocietyActivity |
P102091
|
FINISHED |
| Object | genealogical research |
—
|
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: genealogical research | Statement: [Clan MacNab, clanSocietyActivity, genealogical research]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clanSocietyActivity Context triple: [Clan MacNab, clanSocietyActivity, genealogical research]
-
A.
associatedTribeActivity
Indicates a relationship where a specific activity is linked to, practiced by, or characteristic of a particular tribe.
-
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.
clanType
Indicates the specific category or classification of a clan within a broader clan system or hierarchy.
-
D.
clanCentre
Indicates that one entity serves as the central location, headquarters, or main base for a particular clan or group.
-
E.
communityActivity
chosen
Indicates that an entity participates in, contributes to, or is involved with activities organized for or by a community.
- 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_69d6ab4c6710819097a9d228382dde43 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d915d7109481908bf5fe512bba3c89 |
completed | April 10, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69d9150c18148190bf8152189c0e5fca |
completed | April 10, 2026, 3:19 p.m. |
Created at: April 8, 2026, 9:49 p.m.