Triple
T26362852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aigles de Trois-Rivières |
E660253
|
entity |
| Predicate | isIndependentTeam |
P8371
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Aigles de Trois-Rivières, isIndependentTeam, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isIndependentTeam Context triple: [Aigles de Trois-Rivières, isIndependentTeam, true]
-
A.
hasIndependentTeams
Indicates that an entity possesses or is associated with teams that operate autonomously from other teams or central control.
-
B.
isIndependent
chosen
Indicates that an entity exists, functions, or operates without being controlled, influenced, or determined by another entity.
-
C.
notableIndependentTeam
Indicates that a team is independently organized or operated and is recognized as notable or significant in its context.
-
D.
returnedAsIndependentTeamYear
Indicates the year in which an entity resumed operating as an independent team after previously not being independent.
-
E.
hasIndependent
Indicates that one entity exists, functions, or operates without being controlled, influenced, or determined by another entity.
- 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_69ee8126d52c8190bc0b34337c2c9aa8 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f610293cd88190894969a031f85edd |
completed | May 2, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69f5f800fa9c8190aab0962669fde8ac |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 10:53 p.m.