Triple
T37813191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Woody Woodpecker |
E942704
|
entity |
| Predicate | signatureLaugh |
P51216
|
FINISHED |
| Object | ha-ha-ha-HA-ha |
—
|
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: ha-ha-ha-HA-ha | Statement: [Woody Woodpecker, signatureLaugh, ha-ha-ha-HA-ha]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signatureLaugh Context triple: [Woody Woodpecker, signatureLaugh, ha-ha-ha-HA-ha]
-
A.
signature
Indicates that one entity has provided an official or personal signed endorsement, authorization, or acknowledgment on or for another entity.
-
B.
hasSignatureSmile
Indicates that an entity is characterized by a distinctive or recognizable smile that serves as a notable or identifying feature.
-
C.
signatureFeature
chosen
Indicates that one entity is a defining or characteristic feature that distinctly identifies or typifies another entity.
-
D.
signFeature
Indicates that an entity bears or displays a particular sign, symbol, or distinguishing feature.
-
E.
signsWith
Indicates that one entity formally enters into or endorses an agreement, document, or commitment together with another entity as a co-signer.
- 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_69f76ee8104c8190ab17133ccd8f86e6 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbb9e8108c8190ae1c7940b1677e95 |
completed | May 6, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fbb141605c8190b9c27d70352522db |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:19 p.m.