Triple
T25420513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marsyas |
E636967
|
entity |
| Predicate | contestRule |
P159439
|
FINISHED |
| Object | Marsyas could not match Apollo's added conditions |
—
|
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: Marsyas could not match Apollo's added conditions | Statement: [Marsyas, contestRule, Marsyas could not match Apollo's added conditions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contestRule Context triple: [Marsyas, contestRule, Marsyas could not match Apollo's added conditions]
-
A.
contestRule
chosen
Indicates that there is a rule or regulation governing how a contest is conducted or participated in.
-
B.
challengeRule
Indicates that one entity formally disputes, questions, or seeks to overturn a rule established by another entity or authority.
-
C.
reserveTeamRules
Indicates that there are specific rules or regulations governing the use, composition, or operation of a reserve team.
-
D.
playedUnderRulesOf
Indicates that an activity or game was conducted in accordance with a specified set of rules or regulations.
-
E.
sportRules
Indicates that there is a set of rules or regulations governing how a particular sport is played or conducted.
- 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_69e75db4135881909acc287ebcb7a505 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f6bbb1048190bf951255445aeecc |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f5afd5baac8190bb8ed576813c8591 |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 21, 2026, 1:56 p.m.