Triple
T31779854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kerri Gowler |
E811169
|
entity |
| Predicate | competesAtLevel |
P180985
|
FINISHED |
| Object | 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: international | Statement: [Kerri Gowler, competesAtLevel, international]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: competesAtLevel Context triple: [Kerri Gowler, competesAtLevel, international]
-
A.
competitionLevelOf
Indicates the degree or intensity of competitiveness associated with an entity, event, or context.
-
B.
commonCompetitionLevel
Indicates that two entities participate in competitions that share the same or comparable level of intensity, skill, or ranking.
-
C.
involvesCompetitionLevel
Indicates that the relationship or action specifies or depends on a particular degree or intensity of competition involved.
-
D.
recognizesLevelOfCompetition
Indicates that one entity identifies or acknowledges the degree or intensity of competition associated with another entity or context.
-
E.
competitionLevel
Indicates the degree or intensity of competitive pressure or rivalry present in a given context or interaction.
- 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_69f348e544a48190ab6e700b05f6438c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f75dc25fa08190b371faf36d9fb72c |
completed | May 3, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f758586534819083e91172f4bf5098 |
completed | May 3, 2026, 2:14 p.m. |
| PDg | Predicate description generation | batch_69f75dc140c4819085063d6c4c36ca61 |
completed | May 3, 2026, 2:37 p.m. |
Created at: April 30, 2026, 11:36 p.m.