Triple
T31885040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AMF |
E813984
|
entity |
| Predicate | competitionLevelOrganized |
P746
|
FINISHED |
| Object | elite international |
—
|
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: elite international | Statement: [AMF, competitionLevelOrganized, elite international]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: competitionLevelOrganized Context triple: [AMF, competitionLevelOrganized, elite international]
-
A.
competitionLevelOf
Indicates the degree or intensity of competitiveness associated with an entity, event, or context.
-
B.
competitionOrganized
Indicates that an entity is responsible for arranging, managing, or hosting a competition or contest involving other participants.
-
C.
competitionLevel
chosen
Indicates the degree or intensity of competitive pressure or rivalry present in a given context or interaction.
-
D.
organizedCompetitionIn
Indicates that an entity arranged, managed, or hosted a competition that took place in a specified location.
-
E.
competitionOrganization
Indicates that an organization is responsible for organizing, hosting, or managing a competition or contest.
- 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_69f348ed74bc81909846aaa6a3c7318c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f760a35b988190904e6267553ad2fe |
completed | May 3, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69f75eb3d6f081908c933474eb359e3d |
completed | May 3, 2026, 2:41 p.m. |
Created at: April 30, 2026, 11:57 p.m.