Triple
T14589248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | County Court judge |
E342400
|
entity |
| Predicate | rulesOn |
P95808
|
FINISHED |
| Object | motions |
—
|
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: motions | Statement: [County Court judge, rulesOn, motions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rulesOn Context triple: [County Court judge, rulesOn, motions]
-
A.
rulesBy
Indicates that one entity governs, controls, or exercises authoritative power over another entity.
-
B.
underRule
Indicates that one entity is governed, controlled, or subject to the authority, rules, or dominion of another entity.
-
C.
laysDownRulingOn
chosen
Indicates that an authority formally issues or establishes a decision, judgment, or rule concerning a particular matter or case.
-
D.
rulesDuring
Indicates that one entity holds authority or governance over another throughout a specified time period or interval.
-
E.
regulatingRules
Indicates that one entity establishes or enforces rules or standards that govern or control the behavior, operation, or conditions of 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_69d822ddc0f081909cd8163c7de298cd |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb4237d88819097f3f9a40f5be152 |
completed | April 14, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69de656a953481909a4645b004c40de7 |
completed | April 14, 2026, 4:03 p.m. |
Created at: April 10, 2026, 1:24 a.m.