Triple
T548108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | University of Canberra |
E12775
|
entity |
| Predicate | hasPartnershipType |
P15570
|
FINISHED |
| Object | industry partnerships |
—
|
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: industry partnerships | Statement: [University of Canberra, hasPartnershipType, industry partnerships]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPartnershipType Context triple: [University of Canberra, hasPartnershipType, industry partnerships]
-
A.
hasPartner
Indicates that one entity is in a partner relationship (such as romantic, life, or business partnership) with another entity.
-
B.
hasNetworkPartner
Indicates that an entity is connected to another entity through a formal or recognized network partnership relationship.
-
C.
hasAffiliationType
Indicates that one entity is connected to another through a specified kind or category of affiliation or association.
-
D.
hasTypeOfOrganization
Indicates that an entity is classified as belonging to a particular type or category of organization.
-
E.
coalitionPartnerWith
Indicates that two entities are formally aligned in a cooperative coalition, sharing goals or actions as partners within that coalition.
- 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_69a49334226c81908b0ea1689ef6aa3f |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49900895c819092a131c185a758bf |
completed | March 1, 2026, 7:52 p.m. |
| PD | Predicate disambiguation | batch_69a494b957988190bc269e372df2f0b2 |
completed | March 1, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69a49858abd48190bd4b002a93e4a908 |
completed | March 1, 2026, 7:49 p.m. |
Created at: March 1, 2026, 7:32 p.m.