Triple
T30742757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duchamp |
E782734
|
entity |
| Predicate | hasNotableArtFamilyBranch |
P49773
|
FINISHED |
| Object | Duchamp artistic 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: Duchamp artistic family | Statement: [Duchamp, hasNotableArtFamilyBranch, Duchamp artistic family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableArtFamilyBranch Context triple: [Duchamp, hasNotableArtFamilyBranch, Duchamp artistic family]
-
A.
hasNotableDynastyMember
Indicates that a dynasty includes at least one member who is historically or culturally notable.
-
B.
hasFamilyBranch
chosen
Indicates that one entity is a subdivision, offshoot, or branch within the broader family group or lineage of another entity.
-
C.
notableSurnameBranch
Indicates that a particular family branch is distinguished or noteworthy within a broader surname lineage.
-
D.
hasNotableArtsBearer
Indicates that an entity has a person or group notably associated with it in the field of arts.
-
E.
notableFamilyProduced
Indicates that a notable family is responsible for producing, creating, or giving rise to a particular person, group, or entity.
- 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_69f224aeb1588190897d395e8ed2acb8 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a0056174c908190be99c91a70393e47 |
completed | May 10, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_6a00538e7e08819091ecd4316cd641a1 |
completed | May 10, 2026, 9:44 a.m. |
Created at: April 29, 2026, 8:38 p.m.