Triple
T22979556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CEMS |
E571420
|
entity |
| Predicate | partnersInclude |
P59302
|
FINISHED |
| Object | academic institutions |
—
|
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: academic institutions | Statement: [CEMS, partnersInclude, academic institutions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partnersInclude Context triple: [CEMS, partnersInclude, academic institutions]
-
A.
partnerInOrganizationWith
Indicates that two entities are associated as partners within the same organization or organizational context.
-
B.
collaboratorsInclude
chosen
Indicates that a specified collaborator is included among the collaborators associated with an entity or activity.
-
C.
partnerStructure
Indicates a relationship where one entity is organized, configured, or structured in coordination with, or as a counterpart to, another entity in a partnership context.
-
D.
partnerNation
Indicates that one entity is recognized as a collaborating or allied nation in relation to another entity.
-
E.
partnerInWorkOf
Indicates a collaborative relationship where one entity works together with another on a shared task, project, or professional 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_69e245b3c50481908bb3741ec9f40862 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18294c4c8819083ef85d9cb736613 |
completed | April 29, 2026, 4:01 a.m. |
| PD | Predicate disambiguation | batch_69ef3b9101f48190a06c69dff26c6441 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:49 p.m.