Triple
T9458415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Administrative Court |
E228076
|
entity |
| Predicate | hearsClaimsAgainst |
P18526
|
FINISHED |
| Object | ministers of the Crown |
—
|
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: ministers of the Crown | Statement: [Administrative Court, hearsClaimsAgainst, ministers of the Crown]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hearsClaimsAgainst Context triple: [Administrative Court, hearsClaimsAgainst, ministers of the Crown]
-
A.
hearsCasesAgainst
chosen
Indicates that one party (typically a judicial body or official) formally listens to and considers legal cases brought against another party.
-
B.
hears
Indicates that one entity perceives or detects sounds produced by another entity or source.
-
C.
CanadaClaimsAs
Indicates that Canada asserts ownership, sovereignty, or jurisdiction over the referenced entity or territory.
-
D.
hearsMatters
Indicates that one entity formally considers or listens to issues, cases, or concerns involving another entity.
-
E.
hearsAppealsBy
Indicates that one party has the authority or role to review and decide on appeals submitted by another party.
- 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_69ca843b123881909b0e60028475d12d |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd7f924f3081909dd937cbe6802881 |
completed | April 1, 2026, 8:26 p.m. |
| PD | Predicate disambiguation | batch_69cca55caaa8819089c5138e014892d3 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:52 p.m.