Triple
T4759162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greek Orthodox Katholikon |
E105659
|
entity |
| Predicate | primarySeatingFor |
P48956
|
FINISHED |
| Object | Greek Orthodox clergy |
—
|
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: Greek Orthodox clergy | Statement: [Greek Orthodox Katholikon, primarySeatingFor, Greek Orthodox clergy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primarySeatingFor Context triple: [Greek Orthodox Katholikon, primarySeatingFor, Greek Orthodox clergy]
-
A.
typicalSeat
chosen
Indicates the usual or standard seating position or location associated with an entity in a given context.
-
B.
hasSeating
Indicates that one entity provides or contains seating capacity or seating arrangements for another entity.
-
C.
seatingPosition
Indicates the relative location or arrangement of an entity’s seat with respect to other seats or a reference point in a seating layout.
-
D.
seatOn
Indicates that one entity is positioned or placed on a seat or seating surface associated with another entity.
-
E.
seatCategory
Indicates the classification or type of a seat (e.g., by comfort level, price tier, or section) assigned to an entity.
- 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_69bd43f14cac819081c7c69803648211 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd650c11f4819098cd1f490f711dc8 |
completed | March 20, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69bd6225c9488190afee5bb3619d0365 |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:20 p.m.