Triple
T15800347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scottish court in the Netherlands at Camp Zeist |
E383080
|
entity |
| Predicate | hearingLanguage |
P92545
|
FINISHED |
| Object | English |
—
|
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: English | Statement: [Scottish court in the Netherlands at Camp Zeist, hearingLanguage, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hearingLanguage Context triple: [Scottish court in the Netherlands at Camp Zeist, hearingLanguage, English]
-
A.
languageOfWorkRecognized
Indicates that a work is officially recognized as being created or expressed in a particular language.
-
B.
languageGroupSpoken
chosen
Indicates that a particular language group is spoken or used for communication by an entity.
-
C.
pronunciationLanguage
Indicates the language in which the pronunciation of an entity (such as a word or name) is given.
-
D.
isSpokenLanguage
Indicates that a language is used primarily for oral communication by speakers, as opposed to being only written or symbolic.
-
E.
eligibleLanguage
Indicates that a particular language satisfies the required conditions to be considered valid or allowed in a given context.
- 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_69d86da16e188190b89af699f1ed0bfe |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b4e135b08190b736e77bac5e2bff |
completed | April 16, 2026, 10:07 a.m. |
| PD | Predicate disambiguation | batch_69e0053b847c8190945726c3ddac21cc |
completed | April 15, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:48 a.m.