Triple
T33700025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abigail |
E863429
|
entity |
| Predicate | birthdayPartyType |
P89869
|
FINISHED |
| Object | teenage birthday party |
—
|
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: teenage birthday party | Statement: [Abigail, birthdayPartyType, teenage birthday party]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: birthdayPartyType Context triple: [Abigail, birthdayPartyType, teenage birthday party]
-
A.
offersBirthdayParties
Indicates that one entity provides or hosts birthday party services or events for another entity.
-
B.
namingOccasion
Indicates an event or context in which an entity is given, assigned, or referred to by a particular name.
-
C.
servingOccasion
Indicates the occasion, event, or context during which something (typically food or drink) is served.
-
D.
occasionType
chosen
Indicates the specific kind or category of occasion or event associated with the subject.
-
E.
entryOccasion
Indicates the circumstance, event, or reason that prompts or justifies an entity’s entry or initiation.
- 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_69f3498723a08190ac034339cc78eade |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7051ad6e4819095e82bbd64761803 |
completed | May 3, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69f700fe24e08190998e2c96fbaaad38 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:43 a.m.