Triple
T4170308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Basil Fawlty |
E84545
|
entity |
| Predicate | relationshipWithGuests |
P54490
|
FINISHED |
| Object | often hostile |
—
|
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: often hostile | Statement: [Basil Fawlty, relationshipWithGuests, often hostile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipWithGuests Context triple: [Basil Fawlty, relationshipWithGuests, often hostile]
-
A.
supportsGuest
Indicates that one entity provides assistance, resources, or accommodation to another entity in the role of a guest.
-
B.
returnsAsGuestIn
Indicates that an entity comes back to participate or appear again in a context, but specifically in the role or capacity of a guest rather than a regular or primary member.
-
C.
typicalGuests
Indicates the usual or most common guests associated with a particular host, place, or event.
-
D.
eventParticipant
Indicates that an entity takes part in, is involved in, or participates in a particular event.
-
E.
relationshipPlannedWith
Indicates that a relationship between two entities has been intentionally arranged or scheduled to occur in the future.
- 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_69aed932cab48190b80ffe35f7029ae1 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af02c87cc88190a9ec3712db18a8a7 |
completed | March 9, 2026, 5:26 p.m. |
| PD | Predicate disambiguation | batch_69af018fb0948190a9701b2e8e5d9bac |
completed | March 9, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69af01ee94ec8190aa6dde54d4571c04 |
completed | March 9, 2026, 5:22 p.m. |
Created at: March 9, 2026, 3:44 p.m.