Triple
T9881598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dutch law |
E180819
|
entity |
| Predicate | secondarySource |
P35195
|
FINISHED |
| Object | case law of Dutch courts |
—
|
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: case law of Dutch courts | Statement: [Dutch law, secondarySource, case law of Dutch courts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondarySource Context triple: [Dutch law, secondarySource, case law of Dutch courts]
-
A.
secondarySee
Indicates that one entity is referenced as an additional or alternative point of consultation or viewing in relation to another entity.
-
B.
primarySources
Indicates that one entity serves as an original, authoritative source of information or evidence for another entity.
-
C.
secondaryMedium
Indicates that an entity is associated with an additional, non-primary medium or channel through which it is expressed, delivered, or communicated.
-
D.
hasSecondarySource
chosen
Indicates that an entity is supported, documented, or referenced by a secondary source rather than by a primary or original source.
-
E.
secondaryTo
Indicates that one condition, event, or factor occurs as a consequence of, or is caused by, another primary condition, event, or factor.
- 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_69ca828082cc8190a40f8d299caa6545 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cdb41639c88190a9ef3d950485e3ab |
completed | April 2, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69cd1d810ed48190a252b70e9390c8f3 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:38 p.m.