Triple
T34060334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pilawa coat of arms |
E873475
|
entity |
| Predicate | bearerFamily |
P28764
|
FINISHED |
| Object | Potocki family |
—
|
NE NERFINISHED |
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: Potocki family | Statement: [Pilawa coat of arms, bearerFamily, Potocki family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bearerFamily Context triple: [Pilawa coat of arms, bearerFamily, Potocki family]
-
A.
bearerFamilySocialContext
Indicates the social and familial circumstances or environment surrounding the bearer in relation to others.
-
B.
familyOf
chosen
Indicates a familial relationship exists between the entities, such as by blood, marriage, or adoption.
-
C.
fareFamily
Indicates a relationship that classifies a fare or ticket into a specific fare family or category within a pricing structure.
-
D.
ownerFamily
Indicates that a family has ownership or proprietary rights over a particular entity or resource.
-
E.
hostFamily
Indicates that one entity serves as a host family, providing accommodation, care, or support to another entity, typically for a temporary or exchange-based stay.
- 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_69f349a4af208190afa14888f9c9fb9d |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f75dc25fa08190b371faf36d9fb72c |
completed | May 3, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f758586534819083e91172f4bf5098 |
completed | May 3, 2026, 2:14 p.m. |
Created at: May 1, 2026, 1:52 a.m.