Triple
T6517408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Cow |
E148299
|
entity |
| Predicate | mentionsStory |
P831
|
FINISHED |
| Object | story of the cow commanded to be sacrificed |
—
|
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: story of the cow commanded to be sacrificed | Statement: [The Cow, mentionsStory, story of the cow commanded to be sacrificed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mentionsStory Context triple: [The Cow, mentionsStory, story of the cow commanded to be sacrificed]
-
A.
mentions
chosen
Indicates that one entity refers to, cites, or brings up another entity in some form of communication or content.
-
B.
mentionedWith
Indicates that two entities are mentioned together or in close association within the same context, such as a document, sentence, or conversation.
-
C.
followsStoryOf
Indicates that one narrative, account, or storyline continues from, is based on, or is derived from the events or structure of another.
-
D.
ownerInStory
Indicates that one entity is the owner of another entity within the context or narrative of a specific story.
-
E.
mentionedAs
Indicates that one entity is referred to or cited by name or description in the context of another entity.
- 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_69c687e68e748190baceb9298f32d3ed |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ac0ece2081909c14accef90efd7c |
completed | March 27, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69c68ab98c78819081743e614df04e1d |
completed | March 27, 2026, 1:48 p.m. |
Created at: March 27, 2026, 1:44 p.m.