Triple
T33099823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moroccan railway network |
E847009
|
entity |
| Predicate | hasHighSpeedBrand |
P117796
|
FINISHED |
| Object | Al Boraq |
—
|
NE NERFINISHED |
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: Al Boraq | Statement: [Moroccan railway network, hasHighSpeedBrand, Al Boraq]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHighSpeedBrand Context triple: [Moroccan railway network, hasHighSpeedBrand, Al Boraq]
-
A.
highSpeedBrand
chosen
Indicates that a brand is associated with operating or performing at high speed compared to typical or competing brands.
-
B.
hasBrandType
Indicates that an entity is associated with or categorized under a particular brand type or classification.
-
C.
hasHighSpeedPotential
Indicates that an entity possesses the capability or conditions to achieve or sustain a high rate of speed, even if it is not currently doing so.
-
D.
hasLimitedExpressBrand
Indicates that an entity possesses or is associated with a Limited Express brand designation or service.
-
E.
hasHighSpeedLine
Indicates that there exists a high-speed rail line connection between the related entities.
- 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_69f3495686508190b76bf20fa5e00bf7 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69feb5e66224819083b87c3707a5a5e0 |
completed | May 9, 2026, 4:19 a.m. |
| PD | Predicate disambiguation | batch_69feb3bd700c8190991ed200cd3c04db |
completed | May 9, 2026, 4:10 a.m. |
Created at: May 1, 2026, 1:26 a.m.