Triple
T34544608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Firemen’s Ball |
E886888
|
entity |
| Predicate | intendedModeOfReception |
P3332
|
FINISHED |
| Object | oral performance |
—
|
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: oral performance | Statement: [The Firemen’s Ball, intendedModeOfReception, oral performance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedModeOfReception Context triple: [The Firemen’s Ball, intendedModeOfReception, oral performance]
-
A.
intendedReceiver
Indicates that one entity is the target or designated recipient of something (such as a message, item, or action) originating from another entity.
-
B.
communicationMode
chosen
Indicates the method or channel through which communication between entities is carried out.
-
C.
receiverType
Indicates the category or classification of the entity that receives something (such as a message, resource, or action) in the relationship.
-
D.
hasReception
Indicates that an entity hosts, includes, or is associated with a reception event (such as a formal gathering or welcoming function).
-
E.
primaryReceptionMethod
Indicates the main way in which something is received, accessed, or obtained among multiple possible methods.
- 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_69f349ce5eb881909e431c670944aa68 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fda5003cdc8190a558501271389912 |
completed | May 8, 2026, 8:55 a.m. |
| PD | Predicate disambiguation | batch_69fda05bfc2c819096821a5300e9bb24 |
completed | May 8, 2026, 8:35 a.m. |
Created at: May 1, 2026, 2:02 a.m.