Triple
T22281775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lucie |
E550748
|
entity |
| Predicate | associatedObjectInStory |
P70956
|
FINISHED |
| Object | pocket-handkerchiefs |
—
|
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: pocket-handkerchiefs | Statement: [Lucie, associatedObjectInStory, pocket-handkerchiefs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedObjectInStory Context triple: [Lucie, associatedObjectInStory, pocket-handkerchiefs]
-
A.
associatedWithPersonInStory
Indicates that one entity has a connection or involvement with a specific person within the context of a story.
-
B.
ownerInStory
Indicates that one entity is the owner of another entity within the context or narrative of a specific story.
-
C.
associatedItem
chosen
Indicates that one item is linked or connected to another in a relevant or context-dependent way, without specifying a more precise relationship.
-
D.
partnerInStory
Indicates that two or more entities are partners or collaborators within the context of a specific story or narrative.
-
E.
networkAffiliationInStory
Indicates that, within the context of a story, an entity is affiliated with or belongs to a particular network (such as a media, broadcast, or organizational network).
- 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_69e11e44d538819097c6b8f333af3352 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f14eac0994819088e39a1b5d39cf18 |
completed | April 29, 2026, 12:19 a.m. |
| PD | Predicate disambiguation | batch_69e72ff0363081909f794d19c8a64837 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:40 p.m.