Triple
T13720364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eliza Thomas |
E329014
|
entity |
| Predicate | fieldOfNote |
P39276
|
FINISHED |
| Object | art history (biographical context) |
—
|
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: art history (biographical context) | Statement: [Eliza Thomas, fieldOfNote, art history (biographical context)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fieldOfNote Context triple: [Eliza Thomas, fieldOfNote, art history (biographical context)]
-
A.
fieldOfSignificance
Indicates that something holds particular importance, relevance, or impact within a specified domain, context, or area of interest.
-
B.
notableContributionField
Indicates the field or domain in which an entity has made a significant or noteworthy contribution.
-
C.
notableField
chosen
Indicates the field, discipline, or area of activity for which an entity is especially known or distinguished.
-
D.
fieldOfWork
Indicates the professional or academic domain in which an entity is primarily engaged or specializes.
-
E.
notableWorkFocus
Indicates that a notable work primarily centers on, addresses, or is significantly concerned with a particular subject, theme, or area.
- 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_69d80770b9bc81909f70c8c317d53cff |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dd439a121c81908cae964e7756274c |
completed | April 13, 2026, 7:27 p.m. |
| PD | Predicate disambiguation | batch_69dbbe92d77c81908e0244cffb7f78c5 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:55 p.m.