Triple
T10625956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atalanta (in some traditions) |
E250323
|
entity |
| Predicate | takesPartIn |
P149
|
FINISHED |
| Object | Argonautic expedition |
—
|
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: Argonautic expedition | Statement: [Atalanta (in some traditions), takesPartIn, Argonautic expedition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: takesPartIn Context triple: [Atalanta (in some traditions), takesPartIn, Argonautic expedition]
-
A.
participatedInEvent
chosen
Indicates that an entity took part in or was actively involved in a specific event.
-
B.
invitesParticipationOf
Indicates that one entity actively requests or encourages another entity to take part in an activity, event, or process.
-
C.
hasBeenInvolvedIn
Indicates that an entity has participated in, taken part in, or been connected to a particular event, activity, or situation.
-
D.
participation
Indicates that an entity takes part in, contributes to, or is involved in a shared activity, event, or process with others.
-
E.
participationIncludes
Indicates that a broader participation instance encompasses or contains a more specific participation instance as part of it.
- 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_69d6aa5993448190a493b790b8f85010 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6df80a30c81909f36fe221cf68822 |
completed | April 8, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69d6dd7fae088190973f70c69738af49 |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 8:54 p.m.