Triple
T34502300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | abduction of Europa |
E885789
|
entity |
| Predicate | involvesSeaVoyage |
P64755
|
FINISHED |
| Object | Mediterranean Sea |
—
|
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: Mediterranean Sea | Statement: [abduction of Europa, involvesSeaVoyage, Mediterranean Sea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvesSeaVoyage Context triple: [abduction of Europa, involvesSeaVoyage, Mediterranean Sea]
-
A.
seaVoyages
Indicates that one entity undertakes or is associated with journeys or travel by sea to or involving another entity.
-
B.
involvesVoyageFrom
Indicates a relationship where an event, action, or situation includes a voyage that originates from a specified starting location.
-
C.
associatedWithSeaRoute
Indicates a relationship where something is connected or related to a particular sea route, such as by use, location, or relevance.
-
D.
usesAtSea
Indicates that something is employed, operated, or applied in a maritime or oceanic environment.
-
E.
hasSeaVoyage
chosen
Indicates that an entity undertakes, includes, or is associated with a journey or travel conducted by sea.
- 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_69fdb45537288190b6791078d4a6899f |
completed | May 8, 2026, 10 a.m. |
| PD | Predicate disambiguation | batch_69fdb39ad96481908376d7def9fafc13 |
completed | May 8, 2026, 9:57 a.m. |
Created at: May 1, 2026, 2:01 a.m.