Triple
T19821332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NMS Mircea |
E476200
|
entity |
| Predicate | participates in |
P4470
|
FINISHED |
| Object | international tall ship races |
—
|
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: international tall ship races | Statement: [NMS Mircea, participates in, international tall ship races]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: participates in Context triple: [NMS Mircea, participates in, international tall ship races]
-
A.
participation
chosen
Indicates that an entity takes part in, contributes to, or is involved in a shared activity, event, or process with others.
-
B.
coParticipantIn
Indicates that two or more entities take part together as participants in the same event, activity, or situation.
-
C.
participationIncludes
Indicates that a broader participation instance encompasses or contains a more specific participation instance as part of it.
-
D.
invitesParticipationOf
Indicates that one entity actively requests or encourages another entity to take part in an activity, event, or process.
-
E.
overseesParticipationOf
Indicates that one entity supervises, manages, or has authority over another entity’s involvement in an activity, process, or group.
- 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_69d8e51c7c188190b926f3a2a7b5f881 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e654fee3e48190ae728e49748ad268 |
completed | April 20, 2026, 4:31 p.m. |
| PD | Predicate disambiguation | batch_69e5305bda388190a23b7191768107b1 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:50 p.m.