Triple
T32714489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peale |
E836484
|
entity |
| Predicate | hasNotableArtisticDynasty |
P149016
|
FINISHED |
| Object | Peale 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: Peale family | Statement: [Peale, hasNotableArtisticDynasty, Peale family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableArtisticDynasty Context triple: [Peale, hasNotableArtisticDynasty, Peale family]
-
A.
hasNotableMusicHeritage
Indicates that an entity is recognized for a significant, influential, or historically important tradition or legacy in music.
-
B.
hasNotableDynastyMember
Indicates that a dynasty includes at least one member who is historically or culturally notable.
-
C.
hasNotableArtsBearer
chosen
Indicates that an entity has a person or group notably associated with it in the field of arts.
-
D.
hasNotableWorkDepiction
Indicates that an entity has a notable work in which it is depicted or represented.
-
E.
hasNotableArchitecturalFamily
Indicates that an entity is associated with a prominent or historically significant family known for its architectural work or legacy.
- 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_69f3493446148190819541f3ffe79975 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a0141fceb908190863778741bd4487d |
completed | May 11, 2026, 2:42 a.m. |
| PD | Predicate disambiguation | batch_6a0141a9628c819090c0b24ce052a2fb |
completed | May 11, 2026, 2:40 a.m. |
Created at: May 1, 2026, 1:11 a.m.