Triple
T34717741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Syria at International Mathematical Olympiad |
E1000824
|
entity |
| Predicate | teamMembersPerYear |
P181538
|
FINISHED |
| Object | up to 6 students |
—
|
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: up to 6 students | Statement: [Syria at International Mathematical Olympiad, teamMembersPerYear, up to 6 students]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamMembersPerYear Context triple: [Syria at International Mathematical Olympiad, teamMembersPerYear, up to 6 students]
-
A.
managedTeamToYear
Indicates the specific year during which an entity managed a particular team.
-
B.
teamTenure
Indicates the duration or length of time an entity has been part of a particular team.
-
C.
yearsWithTeam
Indicates the number of years an entity (typically a person) has been associated with or part of a particular team.
-
D.
ceasedWorksTeamOperationsInYear
Indicates that a team stopped conducting its work or operational activities in a specified year.
-
E.
teamStartYear
Indicates the year in which an entity (such as a person or organization) began its association with a particular team.
- 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_69f76dad3f108190a280fd0a2f4ee89a |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f77ffa6b68819090257fed3802c239 |
completed | May 3, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69f7795978c481909e152cd1bd02dd07 |
completed | May 3, 2026, 4:35 p.m. |
| PDg | Predicate description generation | batch_69f77ff804f08190b431a31e6179ace4 |
completed | May 3, 2026, 5:03 p.m. |
Created at: May 3, 2026, 3:59 p.m.