Triple
T35348296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inner House judges |
E1020803
|
entity |
| Predicate | sitIn |
P183048
|
FINISHED |
| Object | Inner House of the Court of Session |
—
|
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: Inner House of the Court of Session | Statement: [Inner House judges, sitIn, Inner House of the Court of Session]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sitIn Context triple: [Inner House judges, sitIn, Inner House of the Court of Session]
-
A.
sitterIn
Indicates that one entity is acting as a sitter (e.g., babysitter, pet sitter, house sitter) for another entity or at a particular place.
-
B.
coSeatIn
Indicates that two or more entities share the same seat or seating location at the same time.
-
C.
maySit
Indicates that one entity is permitted or allowed to sit on or in another entity.
-
D.
canSitIn
Indicates that one entity is able or permitted to sit inside or occupy the seating space of another entity.
-
E.
seatOn
Indicates that one entity is positioned or placed on a seat or seating surface associated with another entity.
- F. None of above. chosen
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_69f76decd95c8190ae428f6a19d535de |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f795b5228c8190adb5bf86e581f70c |
completed | May 3, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69f79104f5b48190a496cdffde8472da |
completed | May 3, 2026, 6:16 p.m. |
| PDg | Predicate description generation | batch_69f79527c7bc8190a69d87bec01f65c8 |
completed | May 3, 2026, 6:34 p.m. |
Created at: May 3, 2026, 4:03 p.m.