Triple
T19927843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Other Mother |
E478972
|
entity |
| Predicate | offersToCoraline |
P63281
|
FINISHED |
| Object | button eyes in exchange for staying |
—
|
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: button eyes in exchange for staying | Statement: [Other Mother, offersToCoraline, button eyes in exchange for staying]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offersToCoraline Context triple: [Other Mother, offersToCoraline, button eyes in exchange for staying]
-
A.
offersFeature
Indicates that one entity provides or makes available a particular feature or capability to another entity.
-
B.
offersObject
chosen
Indicates that a subject provides or makes available a specific object to another party as an offer.
-
C.
offersEdition
Indicates that one entity provides or makes available a particular version or edition of another entity.
-
D.
offersProduct
Indicates that one entity makes a product available to another entity, typically for sale or use.
-
E.
offersViewOf
Indicates that one entity provides a vantage point from which another entity can be seen or visually appreciated.
- 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_69d8e521855c8190b41871700afc8d6a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e659cc1a448190aa98d4a66022457e |
completed | April 20, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69e537f070b481908958e0e5911dcdc1 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:53 p.m.