Triple
T23042946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Alvarez |
E573789
|
entity |
| Predicate | fieldOfWorkOfUser |
P3
|
FINISHED |
| Object | science fiction writing |
—
|
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: science fiction writing | Statement: [John Alvarez, fieldOfWorkOfUser, science fiction writing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fieldOfWorkOfUser Context triple: [John Alvarez, fieldOfWorkOfUser, science fiction writing]
-
A.
fieldOfWork
chosen
Indicates the professional or academic domain in which an entity is primarily engaged or specializes.
-
B.
settingOfWork
Indicates the place, time, or environment in which a creative work’s narrative or events are situated.
-
C.
workFor
Indicates that one entity is employed by or performs work under the authority or direction of another entity.
-
D.
workDescribes
Indicates that one work (such as a document, artwork, or dataset) provides a description or explanatory account of another work.
-
E.
workIncludes
Indicates that a work (such as a project, document, or creative piece) contains or incorporates another specified component, part, or element.
- 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_69e245b9c11481909d06c872214d21af |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18516417081908bf747b20de23a75 |
completed | April 29, 2026, 4:12 a.m. |
| PD | Predicate disambiguation | batch_69ef89d5f71881908b9f9d0c8aab278c |
completed | April 27, 2026, 4:07 p.m. |
Created at: April 17, 2026, 3:54 p.m.