Triple
T33598515
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jadis |
E860643
|
entity |
| Predicate | deliversToOrganization |
P10090
|
FINISHED |
| Object | Rick Grimes |
—
|
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: Rick Grimes | Statement: [Jadis, deliversToOrganization, Rick Grimes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deliversToOrganization Context triple: [Jadis, deliversToOrganization, Rick Grimes]
-
A.
toOrganization
chosen
Indicates a relationship where something or someone is directed, transferred, or associated toward a specific organization as the destination or target.
-
B.
hasOrganizationFor
Indicates that one entity possesses, is associated with, or is responsible for a particular organization in relation to some context or purpose.
-
C.
isDeliveredThrough
Indicates that something is transmitted, conveyed, or provided by means of a specified channel, method, or medium.
-
D.
offersDeliveryTo
Indicates that one entity provides delivery services to another entity or location.
-
E.
orderOrOrganizationServed
Indicates that an entity serves, is affiliated with, or acts on behalf of a particular order or organization.
- 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_69f3497f35908190a2e9bbb9b96c7a3f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f7a8225881908c37c08c3cc86928 |
completed | May 3, 2026, 7:22 a.m. |
| PD | Predicate disambiguation | batch_69f6f6632dfc8190af85e258c8519207 |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:41 a.m.