Triple
T31673509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Lumiere School |
E808335
|
entity |
| Predicate | boysBasketballCompetition |
P17867
|
FINISHED |
| Object | national schedule |
—
|
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: national schedule | Statement: [La Lumiere School, boysBasketballCompetition, national schedule]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boysBasketballCompetition Context triple: [La Lumiere School, boysBasketballCompetition, national schedule]
-
A.
menBasketballNCAAChampionship
Indicates that one entity won the NCAA men's basketball championship in a given year or season.
-
B.
competitionBallFor
Indicates that two or more entities are actively contesting possession or control of the same ball.
-
C.
futsalCompetition
Indicates a competitive event or tournament in the sport of futsal involving participating teams or players.
-
D.
menBasketballConference
Indicates a relationship where a men's basketball team is associated with or competes within a specific athletic conference.
-
E.
competitionOf
chosen
Indicates a relationship where one entity is the competitive event, contest, or rivalry involving 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_69f348dcf5d48190ac25b1365ae717a8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b21e7e088190832a3db585daea1c |
completed | May 3, 2026, 2:25 a.m. |
| PD | Predicate disambiguation | batch_69f6b14faf608190a25b977c0740729c |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 30, 2026, 11:02 p.m.