Triple
T2427772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | T.I.M.E. Association |
E53570
|
entity |
| Predicate | collaborationForm |
P1854
|
FINISHED |
| Object | double degree programs |
—
|
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: double degree programs | Statement: [T.I.M.E. Association, collaborationForm, double degree programs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collaborationForm Context triple: [T.I.M.E. Association, collaborationForm, double degree programs]
-
A.
formOfWork
Indicates that one creative work is a specific form, version, or expression of another related work.
-
B.
helpedForm
Indicates that one entity contributed significantly to the creation, establishment, or founding of another entity.
-
C.
collaborationModel
chosen
Indicates the type or structure of cooperative interaction or joint work established between entities.
-
D.
collaborationArea
Indicates the domain, topic, or field in which two or more entities work together or collaborate.
-
E.
formsWith
Indicates that one entity combines or associates with another to create or constitute a joint structure, group, or configuration.
- 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_69ab495c44d48190b7235b23719bc3f6 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abcc74a5108190a3a9631b0cc1a127 |
completed | March 7, 2026, 6:57 a.m. |
| PD | Predicate disambiguation | batch_69abc5aa1b60819081b87f7985c6cff3 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 6, 2026, 9:42 p.m.