Triple
T1347541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | German U15 |
E28805
|
entity |
| Predicate | collaboratesIn |
P398
|
FINISHED |
| Object | research strategy |
—
|
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: research strategy | Statement: [German U15, collaboratesIn, research strategy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collaboratesIn Context triple: [German U15, collaboratesIn, research strategy]
-
A.
isCollaboration
Indicates that two or more entities are jointly working together toward a shared goal or producing something in partnership.
-
B.
worksWith
chosen
Indicates that two entities collaborate or perform tasks together in a shared work-related context.
-
C.
collaborationModel
Indicates the type or structure of cooperative interaction or joint work established between entities.
-
D.
associatedWork
Indicates that there exists a related or connected work (such as a publication, creative piece, or project) that is meaningfully linked to the subject.
-
E.
notableCollaboration
Indicates a significant joint effort or partnership between entities that produced a noteworthy shared outcome or work.
- 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_69a498571d248190a0ac9eb02d97097f |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c2406c488190b2c04d54d9c5e94c |
completed | March 1, 2026, 10:48 p.m. |
| PD | Predicate disambiguation | batch_69a4bef5857c81909ae984feb85a26ca |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:56 p.m.