Triple
T19075110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Einheitsübersetzung |
E466883
|
entity |
| Predicate | cooperativeEdition |
P96421
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Einheitsübersetzung, cooperativeEdition, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cooperativeEdition Context triple: [Einheitsübersetzung, cooperativeEdition, yes]
-
A.
hasCooperative
Indicates that one entity participates in a cooperative relationship or partnership with another entity.
-
B.
collaborationOf
Indicates a relationship in which two or more entities work together jointly toward a shared goal or outcome.
-
C.
cooperativePlay
Indicates that two or more entities are engaging in a shared, mutually coordinated activity or game toward a common goal.
-
D.
isCooperative
Indicates that an entity engages willingly and constructively in joint actions or relationships with others, working together toward shared goals.
-
E.
publishedInCollaborationWith
chosen
Indicates that an entity was published as a result of a joint effort or partnership with another entity.
- 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_69d8dd04f4488190b1121cc53ef2bfd6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e2e3c7b08190bf6448ead11ba916 |
completed | April 20, 2026, 8:25 a.m. |
| PD | Predicate disambiguation | batch_69e4b99f602881909eeb9c780597e0e6 |
completed | April 19, 2026, 11:16 a.m. |
Created at: April 10, 2026, 12:04 p.m.