Triple
T28373173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Nature of a Crime |
E718687
|
entity |
| Predicate | coAuthoringMode |
P81941
|
FINISHED |
| Object | 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: collaboration | Statement: [The Nature of a Crime, coAuthoringMode, collaboration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coAuthoringMode Context triple: [The Nature of a Crime, coAuthoringMode, collaboration]
-
A.
coAuthorshipType
chosen
Indicates the specific nature or category of the collaborative authorship relationship between two or more contributors.
-
B.
coAuthorField
Indicates that two or more entities have jointly authored a work within the same academic or professional field.
-
C.
hasCoauthor
Indicates that two or more entities have jointly authored the same work or publication.
-
D.
coAuthorAttributionTradition
Indicates that there is a recognized tradition or convention of attributing co-authorship between the related entities.
-
E.
coAuthorAlsoWrote
Indicates that a person who is a co-author of one work also wrote another work, linking shared authorship across multiple creations.
- 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_69eff6ee5afc8190bd7375a29f0cc6c6 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f64e37f7fc819083809149b6661e3c |
completed | May 2, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69f64caede108190a35cc7cbfead866f |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 1:01 a.m.