Triple
T19727398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Two Noble Kinsmen |
E473762
|
entity |
| Predicate | coAuthorshipStatus |
P81941
|
FINISHED |
| Object | collaborative work |
—
|
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: collaborative work | Statement: [The Two Noble Kinsmen, coAuthorshipStatus, collaborative work]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coAuthorshipStatus Context triple: [The Two Noble Kinsmen, coAuthorshipStatus, collaborative work]
-
A.
coAuthorshipType
chosen
Indicates the specific nature or category of the collaborative authorship relationship between two or more contributors.
-
B.
hasCoauthor
Indicates that two or more entities have jointly authored the same work or publication.
-
C.
authorshipStatus
Indicates the current state or condition of an entity’s role as an author in relation to a work (e.g., confirmed, disputed, anonymous, or pending).
-
D.
coAuthorAlsoWrote
Indicates that a person who is a co-author of one work also wrote another work, linking shared authorship across multiple creations.
-
E.
coAuthorAttributionTradition
Indicates that there is a recognized tradition or convention of attributing co-authorship between the related entities.
- 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_69d8e517ebd48190979ee76723bcfadf |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e649f95d5c8190858ba414ff3e95a8 |
completed | April 20, 2026, 3:44 p.m. |
| PD | Predicate disambiguation | batch_69e5304a7aac8190ac13f75f0c008e45 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:47 p.m.