Triple
T10592639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I, Tina |
E250028
|
entity |
| Predicate | collaborativeWriterRole |
P45538
|
FINISHED |
| Object | Kurt Loder as co-writer |
—
|
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: Kurt Loder as co-writer | Statement: [I, Tina, collaborativeWriterRole, Kurt Loder as co-writer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collaborativeWriterRole Context triple: [I, Tina, collaborativeWriterRole, Kurt Loder as co-writer]
-
A.
collaboratorRole
chosen
Indicates the specific function, position, or capacity in which one collaborator participates in a shared activity or project with another.
-
B.
coAuthorshipType
Indicates the specific nature or category of the collaborative authorship relationship between two or more contributors.
-
C.
roleInText
Indicates that an entity participates in a text with a specific function or capacity (e.g., author, editor, character).
-
D.
literaryRole
Indicates the specific narrative or functional role an entity holds within a literary work or text.
-
E.
roleInVox
Indicates that an entity holds a specific role or function within a Vox-related context, such as a project, system, or organization named or described as "Vox."
- 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_69d381c9d3d48190a29ee491e1696a0e |
completed | April 6, 2026, 9:50 a.m. |
| NER | Named-entity recognition | batch_69d5277da8048190add007ca0c37253e |
completed | April 7, 2026, 3:49 p.m. |
| PD | Predicate disambiguation | batch_69d51907b2b881908ab9a8594688ee06 |
completed | April 7, 2026, 2:47 p.m. |
Created at: April 6, 2026, 12:40 p.m.