Triple
T35371300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bachleda-Curuś family |
E1021777
|
entity |
| Predicate | hasNotableMembersInField |
P203186
|
FINISHED |
| Object | arts |
—
|
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: arts | Statement: [Bachleda-Curuś family, hasNotableMembersInField, arts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableMembersInField Context triple: [Bachleda-Curuś family, hasNotableMembersInField, arts]
-
A.
hasNotableMember
Indicates that a group, organization, or collection includes at least one member who is distinguished or noteworthy in some significant way.
-
B.
hasNotableFamilyInField
Indicates that an individual has family members who are recognized or distinguished within a particular professional or academic field.
-
C.
hasMembersWith
Indicates that a group or collection includes one or more specific members that satisfy a given condition or characteristic.
-
D.
hasNotableFieldOfActivityOfMembers
chosen
Indicates that a group or organization is characterized by a particular field or domain in which its members are notably active.
-
E.
hasMembers
Indicates that a group, organization, or collection includes certain entities as its members.
- 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_69f76df000488190ab7c97f565677055 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0324d08190ac5b610cc0f6a38c |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:03 p.m.