Triple
T2989250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State Dining Room (10 Downing Street) |
E80705
|
entity |
| Predicate | typicalGuests |
P44542
|
FINISHED |
| Object | foreign dignitaries |
—
|
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: foreign dignitaries | Statement: [State Dining Room (10 Downing Street), typicalGuests, foreign dignitaries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalGuests Context triple: [State Dining Room (10 Downing Street), typicalGuests, foreign dignitaries]
-
A.
typicalPerformers
Indicates the entities that most commonly or characteristically perform a given action or role.
-
B.
hasNotableGuest
Indicates that an entity has a guest who is distinguished, prominent, or otherwise noteworthy in some significant way.
-
C.
formerCoHostOf
Indicates that one entity previously served as a co-host together with another entity, but no longer holds that co-hosting role.
-
D.
coHostOf
Indicates a relationship where two or more entities jointly host the same event, program, or activity together.
-
E.
typicalParty
Indicates that an entity is a usual, standard, or characteristic participant in a given type of event, situation, or relationship.
- 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_69ad8b16c3488190b47b6aa7a59a335b |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad99dcdb00819092ca5f10396408e0 |
completed | March 8, 2026, 3:46 p.m. |
| PD | Predicate disambiguation | batch_69ad961403108190bbecb8d3608fd4e0 |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97f5d28c8190899d90204dc43428 |
completed | March 8, 2026, 3:38 p.m. |
Created at: March 8, 2026, 2:59 p.m.