Triple
T29403200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tom Mix |
E745706
|
entity |
| Predicate | signatureHorse |
P83579
|
FINISHED |
| Object | Tony the Wonder Horse |
—
|
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 the Wonder Horse | Statement: [Tom Mix, signatureHorse, Tony the Wonder Horse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signatureHorse Context triple: [Tom Mix, signatureHorse, Tony the Wonder Horse]
-
A.
signature
Indicates that one entity has provided an official or personal signed endorsement, authorization, or acknowledgment on or for another entity.
-
B.
signatureNumber
Indicates the identifying number assigned to a specific signature within a document or signing process.
-
C.
signatureImage
Indicates that an entity has an associated image that visually represents its signature.
-
D.
signatureVehicle
chosen
Indicates that the vehicle is the primary or characteristic mode of transportation associated with a particular entity (such as a person, group, or brand).
-
E.
hasSignFor
Indicates that one entity displays, bears, or provides a sign, symbol, or notice that represents, directs attention to, or gives information about 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_69f0a79eb7d081908c67197a5f347e68 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f67d3624248190a36a9b2d2e9778d4 |
completed | May 2, 2026, 10:39 p.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 28, 2026, 2:52 p.m.