Triple
T32875780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Court |
E840923
|
entity |
| Predicate | isToponymicOrLocational |
P2833
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Court, isToponymicOrLocational, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isToponymicOrLocational Context triple: [Court, isToponymicOrLocational, true]
-
A.
isToponymic
chosen
Indicates that something is related to or derived from a place name (a toponym).
-
B.
isOccupationalOrToponymic
Indicates that a name or term is derived either from an occupation (job or role) or from a place (toponymic origin).
-
C.
isToponymIn
Indicates that a place name (toponym) is located within or refers to a specific geographic area or region.
-
D.
hasToponymicUse
Indicates that a term or name is used as a toponym, i.e., as a place name or geographic designation.
-
E.
includesToponym
Indicates that one entity contains or references a place name (toponym) associated with another entity.
- 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_69f349436ee88190b72ee12d0f3f508e |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d16f5cb881908eed141afaaa0b51 |
completed | May 3, 2026, 4:39 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe45554819089cbbd538d992132 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:18 a.m.