Triple
T3253495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Senior Grand Warden |
E68239
|
entity |
| Predicate | traditionallySeated |
P22103
|
FINISHED |
| Object | West in Grand Lodge |
—
|
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: West in Grand Lodge | Statement: [Senior Grand Warden, traditionallySeated, West in Grand Lodge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionallySeated Context triple: [Senior Grand Warden, traditionallySeated, West in Grand Lodge]
-
A.
seatTraditionallyAssociated
Indicates that one entity is a seat or position that is customarily or historically linked with another entity, such as a role, office, or title.
-
B.
seatingPosition
chosen
Indicates the relative location or arrangement of an entity’s seat with respect to other seats or a reference point in a seating layout.
-
C.
hasSeating
Indicates that one entity provides or contains seating capacity or seating arrangements for another entity.
-
D.
settingTraditional
Indicates that something is situated or occurs within a traditional setting, context, or environment.
-
E.
traditionallyOneOf
Indicates that something is customarily or historically considered to belong to a specific set, category, or group.
- 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_69ad858f74408190bcbd07f967cd7bd0 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaf640fd8819083c3c0cc41db2ffc |
completed | March 8, 2026, 5:18 p.m. |
| PD | Predicate disambiguation | batch_69ada41ae74081909a0d1d696be8e35e |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:09 p.m.