Triple
T34502322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | abduction of Europa |
E885789
|
entity |
| Predicate | laterSourcesInclude |
P60514
|
FINISHED |
| Object | Ovid |
—
|
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: Ovid | Statement: [abduction of Europa, laterSourcesInclude, Ovid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterSourcesInclude Context triple: [abduction of Europa, laterSourcesInclude, Ovid]
-
A.
laterSources
chosen
Indicates that the information, claim, or reference is derived from sources that were created or recorded at a later time than the event or material being discussed.
-
B.
sourcesInclude
Indicates that one entity’s content, data, or information is derived from, references, or incorporates material from another specified source.
-
C.
requiresSources
Indicates that something must be supported, justified, or validated by one or more external sources.
-
D.
laterIncludedOn
Indicates that one entity was added to, incorporated into, or featured on another entity at a subsequent time.
-
E.
containsSourceOf
Indicates that one entity includes, holds, or encompasses the origin or cause 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_69f349cc0220819081f154c6964f4dc2 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a002dd4066c8190945a09ed82f44f3f |
completed | May 10, 2026, 7:03 a.m. |
| PD | Predicate disambiguation | batch_6a002b141f4081909999e14988105f3a |
completed | May 10, 2026, 6:52 a.m. |
Created at: May 1, 2026, 2:01 a.m.