Triple
T11821923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conference National |
E281159
|
entity |
| Predicate | numberOfAutomaticPromotionPlaces |
P41170
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [Conference National, numberOfAutomaticPromotionPlaces, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfAutomaticPromotionPlaces Context triple: [Conference National, numberOfAutomaticPromotionPlaces, 1]
-
A.
automaticPromotionPlaces
chosen
Indicates the number or set of positions in a ranking or competition that result in automatic promotion to a higher level or division.
-
B.
playOffPromotionPlaces
Indicates the number or set of league positions that qualify teams for participation in promotion play-off matches.
-
C.
allowsPromotion
Indicates that one entity grants permission or enables another entity to be promoted to a higher status, level, or position.
-
D.
numberOfAutomaticBids
Indicates the total count of automatic bids associated with or placed in a given bidding context.
-
E.
numberOfPlacements
Indicates the total count of times an entity has been placed or assigned within a given context or system.
- 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_69d6ab26aae88190b2489efcb2a24234 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a5e9c50481909b2287a0b23d2094 |
completed | April 10, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69d8a251fc08819095933f1d13c3b742 |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:42 p.m.