Triple
T33802409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Slam |
E866262
|
entity |
| Predicate | usesSecondPersonAddressTo |
P64298
|
FINISHED |
| Object | Tony Hawk |
—
|
NE NERFINISHED |
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: Tony Hawk | Statement: [Slam, usesSecondPersonAddressTo, Tony Hawk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesSecondPersonAddressTo Context triple: [Slam, usesSecondPersonAddressTo, Tony Hawk]
-
A.
usesAddressTo
Indicates that one entity makes use of a particular address (such as a physical, email, or network address) to interact, communicate, or perform an action involving another entity.
-
B.
usesMailingAddressOf
Indicates that one entity uses another entity’s mailing address as its own for receiving mail or official correspondence.
-
C.
addressedWith
Indicates that one entity is referred to or spoken to using a particular name, title, or form of address.
-
D.
usedInStyleOfAddress
chosen
Indicates that one entity is used as a form or style of address when referring to or speaking to another entity.
-
E.
usesAddressingSystem
Indicates that one entity employs or applies a particular addressing system associated with another entity.
- 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_69f3499057fc81909d862b1309a3bd71 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd509e6bc08190b263923c2f40fea3 |
completed | May 8, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69fd4fd1a58881909d4b84de1b24e380 |
completed | May 8, 2026, 2:52 a.m. |
Created at: May 1, 2026, 1:46 a.m.