Triple
T19097938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Forbes |
E467455
|
entity |
| Predicate | clanAssociationType |
P134359
|
FINISHED |
| Object | chiefly line of Clan Forbes |
—
|
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: chiefly line of Clan Forbes | Statement: [House of Forbes, clanAssociationType, chiefly line of Clan Forbes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clanAssociationType Context triple: [House of Forbes, clanAssociationType, chiefly line of Clan Forbes]
-
A.
clanType
Indicates the specific category or classification of a clan within a broader clan system or hierarchy.
-
B.
associatedClan
Indicates a relationship where an entity is linked or belongs to a particular clan, group, or lineage.
-
C.
clanSystem
Indicates a social structure in which individuals are organized into kin-based groups (clans) that define relationships, obligations, and affiliations among them.
-
D.
clanCrestAssociatedWith
Indicates that a particular clan crest is symbolically or traditionally linked to a specific clan or family.
-
E.
clanOrSocietySystem
Indicates a relationship where a group is organized or structured according to a particular clan or society system.
- 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_69d8dd05ac4c8190b1967d8f97f3fb2f |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e36b279c819091a8d51f044bc644 |
completed | April 20, 2026, 8:27 a.m. |
| PD | Predicate disambiguation | batch_69e4b9ac41848190afd0f33b42cebe99 |
completed | April 19, 2026, 11:17 a.m. |
| PDg | Predicate description generation | batch_69e4bfe8a06081909fd5c28a33e9f218 |
completed | April 19, 2026, 11:43 a.m. |
Created at: April 10, 2026, 12:04 p.m.