Triple
T28266445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Hall of Justice |
E712716
|
entity |
| Predicate | principalCourtroomOf |
P30154
|
FINISHED |
| Object | Peace Palace |
—
|
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: Peace Palace | Statement: [Great Hall of Justice, principalCourtroomOf, Peace Palace]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: principalCourtroomOf Context triple: [Great Hall of Justice, principalCourtroomOf, Peace Palace]
-
A.
courtroom
chosen
Indicates a relationship where a legal proceeding or judicial action takes place within or is associated with a specific courtroom.
-
B.
primaryCourthouseFor
Indicates that one entity serves as the main or designated courthouse responsible for handling the legal matters of another entity (such as a jurisdiction or organization).
-
C.
hostCourtOf
Indicates that one entity serves as the venue or location where the court associated with another entity is held or convened.
-
D.
innerCourtBuilding
Indicates that a building is located within the inner court area of another structure or complex.
-
E.
courtName
Indicates the official name assigned to a particular court within a legal or judicial system.
- 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_69efb5216c6881908020dce4aea65381 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec3d3d48190ab2f2b71939e572e |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 27, 2026, 11:15 p.m.