Triple
T7434758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Whitburn F.C. |
E171583
|
entity |
| Predicate | hasCompetitiveLevel |
P5077
|
FINISHED |
| Object | semi-professional or amateur |
—
|
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: semi-professional or amateur | Statement: [Whitburn F.C., hasCompetitiveLevel, semi-professional or amateur]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCompetitiveLevel Context triple: [Whitburn F.C., hasCompetitiveLevel, semi-professional or amateur]
-
A.
isCompetitive
Indicates that one entity engages in rivalry or competition with another, typically striving to outperform or win against it.
-
B.
hasCompetition
Indicates that one entity is in a state of rivalry or contest with another entity, typically competing for the same goal, resource, or advantage.
-
C.
competitionLevel
Indicates the degree or intensity of competitive pressure or rivalry present in a given context or interaction.
-
D.
hasCompetitionElement
Indicates that one entity includes, involves, or is associated with a specific competitive component, aspect, or feature.
-
E.
levelOfCompetition
chosen
Indicates the intensity or degree of competitive pressure present in a given context or interaction.
- 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_69c68a64228c8190affaec2a8127ce7b |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f328cf6081908bea065639fd3620 |
completed | March 27, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69c6f038582c8190bac77c9b5a34b862 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:13 p.m.