Triple
T37766134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rumpole universe |
E941419
|
entity |
| Predicate | featuresChambers |
P61483
|
FINISHED |
| Object | Equity Court |
E1299252
|
NE 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: Equity Court | Statement: [Rumpole universe, featuresChambers, Equity Court]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresChambers Context triple: [Rumpole universe, featuresChambers, Equity Court]
-
A.
featuresCounselFrom
Indicates that one entity includes or presents counsel, advice, or legal representation provided by another entity.
-
B.
chamberServed
Indicates that a particular legislative chamber was the one in which an individual held office or performed their official service.
-
C.
chambersColleague
Indicates that two individuals work as colleagues within the same chamber, office, or professional setting.
-
D.
buildingTypeOfChamber
Indicates the type or category of building in which a given chamber is located or to which it belongs.
-
E.
forChamber
chosen
Indicates that something is intended for use in, associated with, or belonging to a particular chamber.
- F. None of above.
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_69f76ee3251881909bb4451aad50752b |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40e0857d9c81909face62ac69a221c |
completed | June 28, 2026, 8:51 a.m. |
| PD | Predicate disambiguation | batch_6a037a1772e48190ba738c6d11b321e2 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:19 p.m.