Triple
T1114228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Second Petty Bench |
E11059
|
entity |
| Predicate | compositionType |
P23125
|
FINISHED |
| Object | collegial court |
—
|
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: collegial court | Statement: [Second Petty Bench, compositionType, collegial court]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: compositionType Context triple: [Second Petty Bench, compositionType, collegial court]
-
A.
composedIn
Indicates that a creative work was written or musically composed within a particular place or during a specific time period.
-
B.
componentType
Indicates that one entity specifies or classifies the kind or category of component that another entity represents or uses.
-
C.
specialComposition
Indicates that one entity is composed of another in a distinctive or non-standard way, highlighting a particular or exceptional form of composition between them.
-
D.
formationType
chosen
Indicates the specific structural or organizational configuration in which something is arranged, created, or formed.
-
E.
compositionMethod
Indicates the technique or process by which something is composed, created, or constructed.
- 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_69a493252a648190ac48f8742474a5e8 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4bbd92a8c8190a16e55f3f739010f |
completed | March 1, 2026, 10:21 p.m. |
| PD | Predicate disambiguation | batch_69a4bb42990c819080db96478fd4977e |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:43 p.m.