Triple
T8695339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | All Fools' Day |
E206391
|
entity |
| Predicate | typicalPrankTarget |
P66477
|
FINISHED |
| Object | friends |
—
|
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: friends | Statement: [All Fools' Day, typicalPrankTarget, friends]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPrankTarget Context triple: [All Fools' Day, typicalPrankTarget, friends]
-
A.
notablePrankTarget
chosen
Indicates that the subject is a well-known or frequent target of pranks carried out by the object.
-
B.
Prank Encounters
Indicates a relationship where one party orchestrates a deceptive or surprising prank scenario that another party unexpectedly experiences or becomes the target of.
-
C.
typicalFigure
Indicates that one entity serves as a standard or representative example (a typical instance) of the other entity.
-
D.
typicalBlendPartner
Indicates that two entities are commonly or characteristically combined or mixed together as standard or usual partners.
-
E.
aimedAtBy
Indicates that one entity serves as the target or goal toward which another entity directs an action, intention, or focus.
- 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_69ca83555b6c8190abe930dd397e863b |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc582996a0819097ad03097ad1f103 |
completed | March 31, 2026, 11:26 p.m. |
| PD | Predicate disambiguation | batch_69cc4569f9048190b9c86b4c81103d35 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:33 p.m.