Triple
T6097468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Headquarters of the Arab League |
E135911
|
entity |
| Predicate | hasMeetingRoomType |
P15338
|
FINISHED |
| Object | summit conference hall |
—
|
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: summit conference hall | Statement: [Headquarters of the Arab League, hasMeetingRoomType, summit conference hall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMeetingRoomType Context triple: [Headquarters of the Arab League, hasMeetingRoomType, summit conference hall]
-
A.
hasConferenceSpace
chosen
Indicates that an entity provides or includes dedicated space suitable for holding conferences, meetings, or similar gatherings.
-
B.
hasRoom
Indicates that an entity possesses, contains, or is associated with a specific room.
-
C.
hasReadingRoomType
Indicates that an entity (such as a facility or building) has a specific type or category of reading room.
-
D.
hasReservationType
Indicates that an entity is associated with a specific category or type of reservation.
-
E.
hasLoungeType
Indicates that an entity is associated with, or classified by, a particular type or category of lounge.
- 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_69c0087cd3c48190b459848c72d84eb1 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05a987ce081908cbe22940f31ee2f |
completed | March 22, 2026, 9:09 p.m. |
| PD | Predicate disambiguation | batch_69c049f5ac988190b62ba565153aaa35 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:12 p.m.