Triple
T25420512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marsyas |
E636967
|
entity |
| Predicate | contestRule |
P159439
|
FINISHED |
| Object | Apollo played the lyre upside down and sang |
—
|
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: Apollo played the lyre upside down and sang | Statement: [Marsyas, contestRule, Apollo played the lyre upside down and sang]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contestRule Context triple: [Marsyas, contestRule, Apollo played the lyre upside down and sang]
-
A.
challengeRule
Indicates that one entity formally disputes, questions, or seeks to overturn a rule established by another entity or authority.
-
B.
reserveTeamRules
Indicates that there are specific rules or regulations governing the use, composition, or operation of a reserve team.
-
C.
playedUnderRulesOf
Indicates that an activity or game was conducted in accordance with a specified set of rules or regulations.
-
D.
sportRules
Indicates that there is a set of rules or regulations governing how a particular sport is played or conducted.
-
E.
competitionSquadRule
Indicates the rules or constraints governing how squads or teams must be composed or registered for a particular competition.
- F. None of above. chosen
Provenance (4 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_69f4a0f7c6008190ae8cee3e71e19b94 |
completed | May 1, 2026, 12:47 p.m. |
| PDg | Predicate description generation | batch_69f55e497fa081909bc59a7b92c5df59 |
completed | May 2, 2026, 2:15 a.m. |
Created at: April 21, 2026, 1:56 p.m.