Triple
T18318397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daylami |
E438805
|
entity |
| Predicate | competedLevel |
P116444
|
FINISHED |
| Object | international Group/Grade 1 level |
—
|
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: international Group/Grade 1 level | Statement: [Daylami, competedLevel, international Group/Grade 1 level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: competedLevel Context triple: [Daylami, competedLevel, international Group/Grade 1 level]
-
A.
involvesCompetitionLevel
Indicates that the relationship or action specifies or depends on a particular degree or intensity of competition involved.
-
B.
competitionLevelOf
chosen
Indicates the degree or intensity of competitiveness associated with an entity, event, or context.
-
C.
competitionLevel
Indicates the degree or intensity of competitive pressure or rivalry present in a given context or interaction.
-
D.
competedFor
Indicates that an entity took part in a contest, rivalry, or competition in pursuit of another entity (such as a prize, position, or resource).
-
E.
levelOfCompetitionAdministered
Indicates the specific competitive tier or intensity at which an activity, event, or process is formally managed or overseen.
- 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_69d8b916a2d081909e249e4902f6aad9 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e50aa342a881909afcd995405027af |
completed | April 19, 2026, 5:02 p.m. |
| PD | Predicate disambiguation | batch_69e44fe4ee10819086b4142444fca1f5 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:36 a.m.