Triple
T31139143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clan MacDonnell of Antrim |
E793731
|
entity |
| Predicate | modernSeat |
P184867
|
FINISHED |
| Object | Glenarm Castle |
—
|
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: Glenarm Castle | Statement: [Clan MacDonnell of Antrim, modernSeat, Glenarm Castle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernSeat Context triple: [Clan MacDonnell of Antrim, modernSeat, Glenarm Castle]
-
A.
coSeatIn
Indicates that two or more entities share the same seat or seating location at the same time.
-
B.
DASeats
Indicates that an entity assigns or provides seating arrangements for another entity or group.
-
C.
typicalSeat
Indicates the usual or standard seating position or location associated with an entity in a given context.
-
D.
laterSeat
Indicates that one entity is seated in a position that comes after another entity in a specified ordering or sequence of seats.
-
E.
multiSeat
Indicates that an entity is designed to accommodate or provide seating for multiple individuals simultaneously.
- 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_69f224d2b3a48190aa9dd26fbf6eab1a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7b628b17c8190aa058c1a51852a27 |
completed | May 3, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c06f5881908f0b98cad6796478 |
completed | May 3, 2026, 8:49 p.m. |
| PDg | Predicate description generation | batch_69f7b5cadd308190a864245a21b08f9a |
completed | May 3, 2026, 8:53 p.m. |
Created at: April 29, 2026, 9:05 p.m.