Triple
T31340192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soldier of Orange |
E799284
|
entity |
| Predicate | acclaimedAs |
P74359
|
FINISHED |
| Object | classic of Dutch cinema |
—
|
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: classic of Dutch cinema | Statement: [Soldier of Orange, acclaimedAs, classic of Dutch cinema]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: acclaimedAs Context triple: [Soldier of Orange, acclaimedAs, classic of Dutch cinema]
-
A.
acclaimedFor
Indicates that an entity receives widespread praise or recognition specifically for another entity, such as a work, achievement, or contribution.
-
B.
celebratedAs
chosen
Indicates that one entity is regarded, honored, or widely recognized as having a particular role, status, or distinction.
-
C.
hasGivenAcclaimedPerformance
Indicates that an entity has delivered a performance that has received significant praise or critical acclaim.
-
D.
alsoAwardedIn
Indicates that the same award or recognition was given in an additional time, place, or context beyond the primary one.
-
E.
notableAwardRecognition
Indicates that an entity has received or been formally recognized with a notable award or honor.
- 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_69f224e3f6ac8190a13488516abca7c9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69f1340a48190be75fd54fa524d3e |
completed | May 3, 2026, 1:04 a.m. |
| PD | Predicate disambiguation | batch_69f69d1d25e88190a7f57d323574da90 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:16 p.m.