Triple
T30644954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Civil Division of the Court of Appeal |
E780094
|
entity |
| Predicate | hasProcedureRules |
P2846
|
FINISHED |
| Object | Civil Procedure Rules |
—
|
NE NERFINISHED |
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: Civil Procedure Rules | Statement: [Civil Division of the Court of Appeal, hasProcedureRules, Civil Procedure Rules]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProcedureRules Context triple: [Civil Division of the Court of Appeal, hasProcedureRules, Civil Procedure Rules]
-
A.
hasRule
chosen
Indicates that an entity is governed, constrained, or defined by a specific rule or set of rules.
-
B.
hasRuleOver
Indicates that one entity holds authority, control, or governance over another entity.
-
C.
hasRuleFor
Indicates that one entity defines or applies a rule that governs or constrains another entity or situation.
-
D.
hasSpecialProcedure
Indicates that a particular entity is associated with or governed by a designated special procedure or process.
-
E.
hasProceduralRole
Indicates that an entity participates in a process or procedure by fulfilling a specific functional role within that process.
- 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_69f224a50ebc81909b961a94c7f66b12 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69ffff262fac8190a26ed0577e1860bd |
completed | May 10, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69fffcad7d7c8190a4ad7bb35e33bb75 |
completed | May 10, 2026, 3:34 a.m. |
Created at: April 29, 2026, 8:29 p.m.