Triple
T35638194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Samedi Division of the Royal Court |
E1029777
|
entity |
| Predicate | hearingDayOrigin |
P183568
|
FINISHED |
| Object | traditionally sat on Saturdays |
—
|
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: traditionally sat on Saturdays | Statement: [Samedi Division of the Royal Court, hearingDayOrigin, traditionally sat on Saturdays]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hearingDayOrigin Context triple: [Samedi Division of the Royal Court, hearingDayOrigin, traditionally sat on Saturdays]
-
A.
hearingSchedule
Indicates that a formal hearing or legal proceeding is scheduled to occur at a specified time and/or place.
-
B.
heardByCourt
Indicates that a matter, case, or issue has been formally considered or examined by a court.
-
C.
heardBy
Indicates that a sound, message, or communication produced by one entity is perceived or received auditorily by another entity.
-
D.
oralHearingsEndDate
Indicates the date on which the oral hearings in a proceeding or case are concluded.
-
E.
originatingJudge
Indicates the judge who initially handled or issued the original decision or order in a legal matter.
- 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_69f76e087bdc8190a4794bf9c0bd7634 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a01efcc08190bba489a9099b8684 |
completed | May 3, 2026, 7:21 p.m. |
| PD | Predicate disambiguation | batch_69f79e4d885881908a3612e2e75cf84f |
completed | May 3, 2026, 7:13 p.m. |
| PDg | Predicate description generation | batch_69f79f477c4c8190a35cb6d87b1dcbd1 |
completed | May 3, 2026, 7:17 p.m. |
Created at: May 3, 2026, 4:05 p.m.