Triple
T25457416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flitch of bacon tradition |
E637948
|
entity |
| Predicate | usesJury |
P38082
|
FINISHED |
| Object | local jury |
—
|
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: local jury | Statement: [Flitch of bacon tradition, usesJury, local jury]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesJury Context triple: [Flitch of bacon tradition, usesJury, local jury]
-
A.
usesJuries
chosen
Indicates that a legal system, court, or process employs juries to participate in deciding cases or determining outcomes.
-
B.
hasJurors
Indicates that one entity serves as or includes jurors in relation to another entity, typically in the context of a legal case or proceeding.
-
C.
hasJuror
Indicates that a person or legal body is assigned or associated with a specific juror in a judicial context.
-
D.
hasJuryType
Indicates that an entity is associated with, or classified by, a specific type or category of jury.
-
E.
hasSubJuries
Indicates that an entity (typically a main jury or committee) is composed of or associated with one or more subordinate juries.
- 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_69e75db8bab08190baca80b4a8c315fd |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f72884408190b586de6cd827e1d4 |
completed | May 2, 2026, 1:07 p.m. |
| PD | Predicate disambiguation | batch_69f4683b34748190818428489a226124 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 2:10 p.m.