Triple
T35851297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heysen |
E1036360
|
entity |
| Predicate | eponymIsRenownedFor |
P115018
|
FINISHED |
| Object | Australian landscape painting |
—
|
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: Australian landscape painting | Statement: [Heysen, eponymIsRenownedFor, Australian landscape painting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eponymIsRenownedFor Context triple: [Heysen, eponymIsRenownedFor, Australian landscape painting]
-
A.
eponymKnownFor
chosen
Indicates that a person or entity is widely recognized or named as the source or inspiration for something else (such as a concept, place, or object).
-
B.
eponymProfession
Indicates that a person’s profession is the source of an eponym, i.e., a word or name derived from that professional role.
-
C.
eponymIsFrom
Indicates that the name of one entity is derived from or named after another entity.
-
D.
eponymPlayedFor
Indicates that the eponymous person or entity was a member of, or played for, a particular team or organization.
-
E.
eponymBirthPlace
Indicates the place where the person after whom something is named was born.
- 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_69f76e1b4aa481909630373171eb5ec6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aa3883d48190b05e3d2da7a017ae |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d435288190b30b1991fb003121 |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:06 p.m.