Triple
T19076048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abiezrite |
E466904
|
entity |
| Predicate | traditionViewsAs |
P13958
|
FINISHED |
| Object | historical clan |
—
|
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: historical clan | Statement: [Abiezrite, traditionViewsAs, historical clan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionViewsAs Context triple: [Abiezrite, traditionViewsAs, historical clan]
-
A.
viewOnTradition
Indicates an entity’s stance, perspective, or attitude toward a particular tradition or set of traditions.
-
B.
traditionAscribes
chosen
Indicates that a tradition attributes or assigns a particular quality, role, origin, or action to an entity.
-
C.
mainTradition
Indicates that one entity represents the primary or dominant tradition associated with another entity.
-
D.
traditionalView
Indicates that one entity holds or represents a conventional, long-established perspective or interpretation about another entity or topic.
-
E.
variantTraditions
Indicates that there exist differing or alternative traditions or customary practices associated with the same subject or context.
- 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_69d8dd04f4488190b1121cc53ef2bfd6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e2e49c7c8190b6ce7b918086b23c |
completed | April 20, 2026, 8:25 a.m. |
| PD | Predicate disambiguation | batch_69e4b99f602881909eeb9c780597e0e6 |
completed | April 19, 2026, 11:16 a.m. |
Created at: April 10, 2026, 12:04 p.m.