Triple
T13085051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UNITE! university alliance |
E310308
|
entity |
| Predicate | hasCollaborationMode |
P98693
|
FINISHED |
| Object | joint projects |
—
|
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: joint projects | Statement: [UNITE! university alliance, hasCollaborationMode, joint projects]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCollaborationMode Context triple: [UNITE! university alliance, hasCollaborationMode, joint projects]
-
A.
isCollaboration
Indicates that two or more entities are jointly working together toward a shared goal or producing something in partnership.
-
B.
isCollaborative
Indicates that two or more entities work together jointly toward a shared goal or outcome.
-
C.
supportsCollaborationFeature
Indicates that one entity provides or enables a collaboration-related feature for another entity or within a system.
-
D.
hasCoopMode
chosen
Indicates that something supports or includes a cooperative mode of operation or gameplay involving multiple participants working together.
-
E.
hasCollaborationTopic
Indicates that two or more entities are engaged in a collaboration focused on a specified topic or subject area.
- 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_69d806a733548190989cfd4ce981ca33 |
completed | April 9, 2026, 8:05 p.m. |
| NER | Named-entity recognition | batch_69d981361e8c819099376435aa3a7aa3 |
completed | April 10, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69d9803f6c508190bfadfbc2d00c2c64 |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:02 p.m.