Triple
T21549611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sa Sartiglia |
E531725
|
entity |
| Predicate | goalOfTournament |
P46673
|
FINISHED |
| Object | pierce the star with a sword |
—
|
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: pierce the star with a sword | Statement: [Sa Sartiglia, goalOfTournament, pierce the star with a sword]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: goalOfTournament Context triple: [Sa Sartiglia, goalOfTournament, pierce the star with a sword]
-
A.
competitionGoal
chosen
Indicates that one entity’s objective or desired outcome is defined in the context of a competition involving another entity.
-
B.
goalOfSide1
Indicates that the specified entity represents the objective or intended outcome pursued by the first side/party in a two-sided interaction or conflict.
-
C.
goalIn
Indicates that one entity’s objective, aim, or intended outcome is located within, directed toward, or achieved inside another entity or context.
-
D.
goalType
Indicates the specific category or nature of a goal associated with an entity or action.
-
E.
playerOfTheTournament
Indicates that an entity has been recognized as the most outstanding performer in a particular tournament.
- 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_69e0c460232c81908de2c3819d17c00e |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eeb5917fb88190a8d37831cced75dc |
completed | April 27, 2026, 1:02 a.m. |
| PD | Predicate disambiguation | batch_69e6320766308190ba5dca2f7c826aa4 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:28 p.m.