Triple
T7136998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miscellanies in Prose and Verse |
E166329
|
entity |
| Predicate | collaborativeWork |
P75049
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Miscellanies in Prose and Verse, collaborativeWork, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collaborativeWork Context triple: [Miscellanies in Prose and Verse, collaborativeWork, true]
-
A.
collaborationOf
Indicates a relationship in which two or more entities work together jointly toward a shared goal or outcome.
-
B.
collaborationAspect
Indicates a specific characteristic, dimension, or feature of how entities collaborate or work together.
-
C.
collaborationAt
Indicates that two or more entities are working together or jointly engaged in an activity, project, or context at a specific place, organization, or event.
-
D.
hasCollaboratedIn
Indicates that two or more entities have worked together on a shared project, task, or activity.
-
E.
collaborationStartWork
Indicates the point in time when a collaborative effort between entities begins or is initiated.
- 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_69c68884a9388190af42f90d1c1a7151 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e6939b788190929e92ff481f2ee4 |
completed | March 27, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c932888190b125ca3785b18553 |
completed | March 27, 2026, 8 p.m. |
| PDg | Predicate description generation | batch_69c6e4a213508190a40aca39f9eee7d5 |
completed | March 27, 2026, 8:12 p.m. |
Created at: March 27, 2026, 2:45 p.m.