Triple
T16611909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edward K. Milkis |
E403592
|
entity |
| Predicate | hasNotableCollaborationPeriod |
P65841
|
FINISHED |
| Object | 1970s |
—
|
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: 1970s | Statement: [Edward K. Milkis, hasNotableCollaborationPeriod, 1970s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableCollaborationPeriod Context triple: [Edward K. Milkis, hasNotableCollaborationPeriod, 1970s]
-
A.
hasNotableCollaborationType
Indicates a specific kind or category of significant collaborative relationship that exists between entities.
-
B.
notableCollaboration
Indicates a significant joint effort or partnership between entities that produced a noteworthy shared outcome or work.
-
C.
hasCollaboratedIn
Indicates that two or more entities have worked together on a shared project, task, or activity.
-
D.
hasSubsequentCollaboration
Indicates that one entity engages in a follow-up or later collaboration with another entity after an initial joint activity or partnership.
-
E.
collaborationPeriod
chosen
Indicates the time span during which two or more entities are actively engaged in a collaborative relationship or joint activity.
- 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_69d883880d0c81908b5fcd454e767b60 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e36096356c819092815d64db041793 |
completed | April 18, 2026, 10:44 a.m. |
| PD | Predicate disambiguation | batch_69e296aabc508190b3836a91b49113ad |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:17 a.m.