Triple
T37171979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vidkun Quisling |
E920938
|
entity |
| Predicate | collaboratorWith |
P59302
|
FINISHED |
| Object | Nazi Germany |
—
|
NE NERFINISHED |
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: Nazi Germany | Statement: [Vidkun Quisling, collaboratorWith, Nazi Germany]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collaboratorWith Context triple: [Vidkun Quisling, collaboratorWith, Nazi Germany]
-
A.
collaborationOf
Indicates a relationship in which two or more entities work together jointly toward a shared goal or outcome.
-
B.
collaboratorName
Indicates that the predicate specifies the name of a person or entity who collaborates with another in some shared activity or project.
-
C.
collaboratorRole
Indicates the specific function, position, or capacity in which one collaborator participates in a shared activity or project with another.
-
D.
collaboratesVia
Indicates that two or more entities work together or coordinate their activities through a specified medium, channel, or intermediary.
-
E.
collaboratorsInclude
chosen
Indicates that a specified collaborator is included among the collaborators associated with an entity or 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_69f76ea16f288190b445aa1604d996f4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fbaebc8f2c8190b94f1b4a3ec92e8c |
completed | May 6, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69fbadf1e6008190a71bbd196ba06844 |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:15 p.m.