Triple
T13471538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | small claims division |
E311639
|
entity |
| Predicate | oftenHears |
P73986
|
FINISHED |
| Object | cases in a single hearing |
—
|
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: cases in a single hearing | Statement: [small claims division, oftenHears, cases in a single hearing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenHears Context triple: [small claims division, oftenHears, cases in a single hearing]
-
A.
usuallyHears
Indicates that one entity typically or habitually perceives sounds produced by another entity.
-
B.
hears
Indicates that one entity perceives or detects sounds produced by another entity or source.
-
C.
oftenSays
Indicates that one entity frequently makes a particular statement or remark, or regularly expresses a certain idea or phrase.
-
D.
mayHear
Indicates that one entity is permitted or able to hear sounds, speech, or audio produced by another entity.
-
E.
hearsMatters
chosen
Indicates that one entity formally considers or listens to issues, cases, or concerns involving 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_69d806a938b8819097ec43a2229fc7f9 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaf22e5f88190b1078f006c8ef7c0 |
completed | April 12, 2026, 2:41 p.m. |
| PD | Predicate disambiguation | batch_69dbadfddefc81909ef7fde23b181b5c |
completed | April 12, 2026, 2:36 p.m. |
Created at: April 9, 2026, 9:42 p.m.