Triple
T1291476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carnegie family |
E27556
|
entity |
| Predicate | hasClanStatus |
P28158
|
FINISHED |
| Object | recognized Lowland family |
—
|
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: recognized Lowland family | Statement: [Carnegie family, hasClanStatus, recognized Lowland family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClanStatus Context triple: [Carnegie family, hasClanStatus, recognized Lowland family]
-
A.
hasClanChiefStatus
Indicates that an entity holds the role or status of being the chief or leader of a clan.
-
B.
hasClanSeat
Indicates that an entity holds an official seat or position within a particular clan.
-
C.
associatedClan
Indicates a relationship where an entity is linked or belongs to a particular clan, group, or lineage.
-
D.
clanSystem
Indicates a social structure in which individuals are organized into kin-based groups (clans) that define relationships, obligations, and affiliations among them.
-
E.
hasTribalEnrollment
Indicates that an entity is formally enrolled as a member of a specific tribe or tribal nation.
- F. None of above. chosen
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_69a496d4ec448190ad653b2590c46711 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c0d7d15081909d3af19b9297f1cc |
completed | March 1, 2026, 10:42 p.m. |
| PD | Predicate disambiguation | batch_69a4bee41ca08190b0ad6f7ea40c0b62 |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4bfa205ec81909d8170b398345615 |
completed | March 1, 2026, 10:37 p.m. |
Created at: March 1, 2026, 7:51 p.m.