Triple
T4878294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siris |
E109256
|
entity |
| Predicate | contextInAuthorCareer |
P57383
|
FINISHED |
| Object | late work of George Berkeley |
—
|
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: late work of George Berkeley | Statement: [Siris, contextInAuthorCareer, late work of George Berkeley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contextInAuthorCareer Context triple: [Siris, contextInAuthorCareer, late work of George Berkeley]
-
A.
workInAuthorCareer
Indicates that an author’s professional work or role occurs within and is part of their overall writing career.
-
B.
authorLifespanContext
Indicates the temporal or historical context of an author’s life span in relation to other events, periods, or entities.
-
C.
workInChronologyOfAuthor
chosen
Indicates that a work appears within, and is ordered as part of, the chronological sequence of an author's creations or publications.
-
D.
authorOccupation
Indicates the professional role or job that an author holds or is associated with.
-
E.
describesCareerOf
Indicates that one entity provides a description or characterization of the professional career of another 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_69bd440e9d64819083e82cf33b4d9570 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6dbd69d48190a8397d67af8f5fc8 |
completed | March 20, 2026, 3:54 p.m. |
| PD | Predicate disambiguation | batch_69bd6c2be5e881909f6ec9c3bcde49f3 |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:27 p.m.