Triple
T21087520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | US Nérac |
E519539
|
entity |
| Predicate | hasTeamLevel |
P5182
|
FINISHED |
| Object | community-level teams |
—
|
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: community-level teams | Statement: [US Nérac, hasTeamLevel, community-level teams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTeamLevel Context triple: [US Nérac, hasTeamLevel, community-level teams]
-
A.
supportsTeamLevel
Indicates that one entity provides assistance, resources, or endorsement to a team as a whole rather than to individual members.
-
B.
controlsTeamLevel
Indicates that one entity has authority or decision-making power over the overall direction, strategy, or functioning of a team.
-
C.
teamLevel
chosen
Indicates the hierarchical rank or tier at which a team operates within an organization, competition, or structure.
-
D.
hasTeamFor
Indicates that an entity possesses, is associated with, or is responsible for a specific team designated for a particular purpose or context.
-
E.
hasHomeTeamLevel
Indicates that an entity is associated with the competitive level or tier of the home team involved in a game or event.
- 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_69e0b507dd9081908fb8bfcbef4c8b46 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7094be9388190b004fda23f301397 |
completed | April 21, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69e5dbfcd5e881908f1e4e0d2d237856 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:50 p.m.