Triple
T8323929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Evenings at Home |
E194900
|
entity |
| Predicate | coAuthorshipType |
P81941
|
FINISHED |
| Object | sibling collaboration |
—
|
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: sibling collaboration | Statement: [Evenings at Home, coAuthorshipType, sibling collaboration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coAuthorshipType Context triple: [Evenings at Home, coAuthorshipType, sibling collaboration]
-
A.
hasCoauthor
Indicates that two or more entities have jointly authored the same work or publication.
-
B.
coAuthorAlsoWrote
Indicates that a person who is a co-author of one work also wrote another work, linking shared authorship across multiple creations.
-
C.
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.
-
D.
collaborationOf
Indicates a relationship in which two or more entities work together jointly toward a shared goal or outcome.
-
E.
collaboratorRole
Indicates the specific function, position, or capacity in which one collaborator participates in a shared activity or project with another.
- F. None of above. chosen
Provenance (4 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_69ca82e7a8a88190a32bb5cc0feb012d |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7f7cf49c8190b8440ff01926a66a |
completed | March 31, 2026, 8:02 a.m. |
| PD | Predicate disambiguation | batch_69cb70bf689c8190a9d9b6b872abf53d |
completed | March 31, 2026, 6:59 a.m. |
| PDg | Predicate description generation | batch_69cb77690720819099de1e22b84a9563 |
completed | March 31, 2026, 7:27 a.m. |
Created at: March 30, 2026, 5:56 p.m.