Triple
T34502320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | abduction of Europa |
E885789
|
entity |
| Predicate | earliestSourcesInclude |
P60063
|
FINISHED |
| Object | Homer |
—
|
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: Homer | Statement: [abduction of Europa, earliestSourcesInclude, Homer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earliestSourcesInclude Context triple: [abduction of Europa, earliestSourcesInclude, Homer]
-
A.
earliestFullSource
Indicates that one entity is the earliest (in time or order) complete source or origin for another entity.
-
B.
earliestExtendedSource
chosen
Indicates that one entity is the earliest or first-occurring instance among a set of extended sources related to another entity.
-
C.
earliestDocumentsDate
Indicates the earliest date on which the associated documents were created, recorded, or became valid.
-
D.
sourcesInclude
Indicates that one entity’s content, data, or information is derived from, references, or incorporates material from another specified source.
-
E.
isContemporarySourceFor
Indicates that one entity serves as a source of information that originates from the same time period as the other entity or event it documents.
- 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_69fbbc49da8c8190902bbb05d2477cab |
completed | May 6, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69fbb13f34b08190bbbb220ac1e6e666 |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 1, 2026, 2:01 a.m.