Triple
T32637358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lucy |
E834380
|
entity |
| Predicate | ownershipStatusInStory |
P61752
|
FINISHED |
| Object | owned by Wendy |
—
|
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: owned by Wendy | Statement: [Lucy, ownershipStatusInStory, owned by Wendy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ownershipStatusInStory Context triple: [Lucy, ownershipStatusInStory, owned by Wendy]
-
A.
ownerInStory
chosen
Indicates that one entity is the owner of another entity within the context or narrative of a specific story.
-
B.
ownershipStatusInSeries
Indicates the type or state of ownership an entity holds within a particular series or collection.
-
C.
relationshipStatusInStory
Indicates the type or state of the relationship between entities as it exists within the context of a specific story or narrative.
-
D.
isStoried
Indicates that something has a rich history, reputation, or legacy built up over time, often marked by notable events or traditions.
-
E.
primaryUserInStory
Indicates that a particular user is the main or central user involved in the context of a given story.
- 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_69f3492dc2308190a88c6e30a3f3f576 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
Created at: May 1, 2026, 1:07 a.m.