Triple
T32020130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eve |
E817658
|
entity |
| Predicate | designedByInStory |
P97519
|
FINISHED |
| Object | Buy n Large Corporation |
—
|
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: Buy n Large Corporation | Statement: [Eve, designedByInStory, Buy n Large Corporation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedByInStory Context triple: [Eve, designedByInStory, Buy n Large Corporation]
-
A.
designedBy
Indicates that one entity is the creator, planner, or architect responsible for the form or structure of another entity.
-
B.
creatorInStory
chosen
Indicates that one entity is the creator (e.g., author, originator, or maker) of another entity within the context of a specific story or narrative.
-
C.
designedIn
Indicates that something was created, planned, or conceived during a particular time period or at a specific location.
-
D.
illustratorOf
Indicates that one entity serves as the illustrator or creator of the visual artwork for another entity, such as a book, article, or other work.
-
E.
designSucceededBy
Indicates that one design is followed or replaced by another design in a temporal or version sequence.
- 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_69f348fb04e4819081f4eab040ed7959 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe21b0cba48190b56c39e9f1c0eafa |
completed | May 8, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69fe204576848190aecf204e2adba5dc |
completed | May 8, 2026, 5:41 p.m. |
Created at: May 1, 2026, 12:16 a.m.