Triple
T10497583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Section Paloise |
E247578
|
entity |
| Predicate | promotionToTop14 |
P69707
|
FINISHED |
| Object | 2015 |
—
|
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: 2015 | Statement: [Section Paloise, promotionToTop14, 2015]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: promotionToTop14 Context triple: [Section Paloise, promotionToTop14, 2015]
-
A.
promotionTo
Indicates that one entity is elevated or advanced to a higher rank, position, or status relative to another entity or context.
-
B.
promotedIn
Indicates that an entity was advanced to a higher rank, position, or status during a specified time or event.
-
C.
promotionOver
Indicates that one entity has been promoted to a higher rank, position, or status relative to another entity.
-
D.
promotedBackToTopFlight
chosen
Indicates that an entity has been moved back up from a lower division or level to the highest (top-flight) tier in a competitive hierarchy.
-
E.
promotedWith
Indicates that one entity is advertised, marketed, or publicized together with another entity as part of the same promotional effort.
- 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_69d381c309b88190af78aa681cf6a4c2 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d5098d8ac481909c4adedbc4ad1c03 |
completed | April 7, 2026, 1:41 p.m. |
| PD | Predicate disambiguation | batch_69d4fb8e24ac8190912c9f11b8bd3084 |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:25 p.m.