Triple
T293073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | District Court of Guam |
E6035
|
entity |
| Predicate | hasJudgeType |
P10518
|
FINISHED |
| Object | district judge |
—
|
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: district judge | Statement: [District Court of Guam, hasJudgeType, district judge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasJudgeType Context triple: [District Court of Guam, hasJudgeType, district judge]
-
A.
hasTypeOfCourt
Indicates that an entity is associated with or classified by a specific type or category of court.
-
B.
hasTypeOfCase
Indicates that an entity is associated with or classified under a particular type or category of case.
-
C.
hasJurisdictionOver
Indicates that one authority or governing body holds legal power or control to make and enforce decisions over another entity, area, or matter.
-
D.
judgesTerm
Indicates that one entity formally evaluates or makes a judgment about a specific term or expression.
-
E.
judge
Indicates that one entity evaluates, forms an opinion about, or makes a decision regarding another entity or situation.
- F. None of above. chosen
Provenance (4 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_69a2e79114b081909490b3bf5a5dbb51 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2ea0dd1dc8190aecd5afdeb2fd74b |
completed | Feb. 28, 2026, 1:13 p.m. |
| PD | Predicate disambiguation | batch_69a2e934b4408190b53a17f57a02df65 |
completed | Feb. 28, 2026, 1:10 p.m. |
| PDg | Predicate description generation | batch_69a2ea07e3bc8190bae593b3264de211 |
completed | Feb. 28, 2026, 1:13 p.m. |
Created at: Feb. 28, 2026, 1:06 p.m.