Triple
T528886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Court of Session (in peerage matters) |
E10984
|
entity |
| Predicate | typeOfCase |
P4217
|
FINISHED |
| Object | civil case |
—
|
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: civil case | Statement: [Court of Session (in peerage matters), typeOfCase, civil case]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfCase Context triple: [Court of Session (in peerage matters), typeOfCase, civil case]
-
A.
typeOfLaw
Indicates that one entity is a specific category or kind of law to which the other entity pertains.
-
B.
legalCase
Indicates a relationship where a formal legal dispute or proceeding exists between parties, typically adjudicated by a court or similar authority.
-
C.
typeOfClaim
Indicates the specific category or nature of a claim being made in relation to an entity or statement.
-
D.
hasTypeOfCase
chosen
Indicates that an entity is associated with or classified under a particular type or category of case.
-
E.
hasTypeOfCourt
Indicates that an entity is associated with or classified by a specific type or category of court.
- 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_69a2e84b16c4819088d284c47c3a7968 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f1d39b4c81909f265b3501b5ec1d |
completed | Feb. 28, 2026, 1:46 p.m. |
| PD | Predicate disambiguation | batch_69a2f01ac3ec8190a94a05955532c7fa |
completed | Feb. 28, 2026, 1:39 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.