Triple
T22964871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Mathematical Olympiad |
E571010
|
entity |
| Predicate | problemAreas |
P19540
|
FINISHED |
| Object | algebra |
—
|
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: algebra | Statement: [International Mathematical Olympiad, problemAreas, algebra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: problemAreas Context triple: [International Mathematical Olympiad, problemAreas, algebra]
-
A.
problems
Indicates that one entity has issues, difficulties, or complications associated with or caused by another entity.
-
B.
structuralIssues
Indicates that there are problems or deficiencies in the design, construction, or integrity of a structure or system.
-
C.
issues
Indicates that an entity formally produces, releases, or distributes something, such as a document, order, or resource, making it officially available.
-
D.
keyIssueArea
chosen
Indicates that something is a primary topic, domain, or field that is central or especially important within a broader context or discussion.
-
E.
problemType
Indicates the specific category or classification of a problem within a defined problem space or system.
- 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_69e245b212a88190b5259caf51606084 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f181f763688190aab8f444a1a71577 |
completed | April 29, 2026, 3:58 a.m. |
| PD | Predicate disambiguation | batch_69ef3b9101f48190a06c69dff26c6441 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:47 p.m.