Triple
T14552215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Vision of Fire |
E341444
|
entity |
| Predicate | coAuthorProfession |
P938
|
FINISHED |
| Object | actress |
—
|
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: actress | Statement: [A Vision of Fire, coAuthorProfession, actress]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coAuthorProfession Context triple: [A Vision of Fire, coAuthorProfession, actress]
-
A.
coAuthorshipType
Indicates the specific nature or category of the collaborative authorship relationship between two or more contributors.
-
B.
authorOccupation
chosen
Indicates the professional role or job that an author holds or is associated with.
-
C.
coAuthorAlsoWrote
Indicates that a person who is a co-author of one work also wrote another work, linking shared authorship across multiple creations.
-
D.
coAuthorNationality
Indicates that two or more co-authors of a work share the same nationality or have nationalities being related in the context of their co-authorship.
-
E.
hasCoauthor
Indicates that two or more entities have jointly authored the same work or publication.
- 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_69d822db9c8481908213ceb39585f792 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb2ee34208190bf040a513767c958 |
completed | April 14, 2026, 9:34 p.m. |
| PD | Predicate disambiguation | batch_69de5c57489c8190b57917be1dba6ae6 |
completed | April 14, 2026, 3:25 p.m. |
Created at: April 10, 2026, 1:23 a.m.