Triple
T48989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Court of Oyer and Terminer |
E962
|
entity |
| Predicate | operatingLanguage |
P1252
|
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: [Court of Oyer and Terminer, operatingLanguage, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatingLanguage Context triple: [Court of Oyer and Terminer, operatingLanguage, English]
-
A.
languagesSpoken
Indicates that an entity is able to communicate using one or more specified languages.
-
B.
languageBranch
Indicates that one language belongs to, or is classified under, a broader linguistic branch or subgroup.
-
C.
primaryLanguageOf
chosen
Indicates that a specified language is the main or official language used by a particular entity (such as a person, organization, or region).
-
D.
officialLanguage
Indicates that a particular language has been formally designated by an authority as the official language used for government, legal, or administrative purposes in a given jurisdiction.
-
E.
isWidelySpokenIn
Indicates that a language is spoken by a large portion of the population across many regions or communities within a specified area.
- 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_69a2480baefc81909951b14058479aa2 |
completed | Feb. 28, 2026, 1:42 a.m. |
| NER | Named-entity recognition | batch_69a24c1a5c14819088748317a3f262c8 |
completed | Feb. 28, 2026, 1:59 a.m. |
| PD | Predicate disambiguation | batch_69a24abfa7bc8190932c137a823efcb6 |
completed | Feb. 28, 2026, 1:54 a.m. |
Created at: Feb. 28, 2026, 1:47 a.m.