Triple
T36889297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prior General of the Carthusian Order |
E911696
|
entity |
| Predicate | symbolicSeat |
P148974
|
FINISHED |
| Object | cell and cloister of the Grande Chartreuse |
—
|
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: cell and cloister of the Grande Chartreuse | Statement: [Prior General of the Carthusian Order, symbolicSeat, cell and cloister of the Grande Chartreuse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: symbolicSeat Context triple: [Prior General of the Carthusian Order, symbolicSeat, cell and cloister of the Grande Chartreuse]
-
A.
hasSeatSymbol
chosen
Indicates that an entity is associated with a specific seat designation or symbol representing its seating position.
-
B.
seatIs
Indicates that one entity functions as the seat or seating position of another entity.
-
C.
seatOn
Indicates that one entity is positioned or placed on a seat or seating surface associated with another entity.
-
D.
seatSince
Indicates that an entity has held a particular seat, position, or place continuously since a specified point in time.
-
E.
coSeatIn
Indicates that two or more entities share the same seat or seating location at the same time.
- 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_69f76e8335908190b77e7e11d0e80820 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:13 p.m.