Triple
T9562649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mitsubishi CRJ700 |
E230711
|
entity |
| Predicate | alsoKnownAs |
P39
|
FINISHED |
| Object | CRJ700 |
E230711
|
NE 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: CRJ700 | Statement: [Mitsubishi CRJ700, alsoKnownAs, CRJ700]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: CRJ700 Context triple: [Mitsubishi CRJ700, alsoKnownAs, CRJ700]
-
A.
Mitsubishi CRJ700
chosen
The Mitsubishi CRJ700 is a regional jet airliner designed for short- to medium-haul routes, commonly used by regional carriers around the world.
-
B.
Bombardier CRJ family
The Bombardier CRJ family is a series of regional jet airliners widely used by airlines around the world for short- to medium-haul routes.
-
C.
Embraer ERJ 145
The Embraer ERJ 145 is a Brazilian-built regional jet airliner widely used for short-haul passenger and military transport operations.
-
D.
Embraer 175
The Embraer 175 is a regional jet airliner designed for short- to medium-haul routes, widely used by airlines for its efficient performance and comfortable 70–88 seat cabin.
-
E.
Fokker 70
The Fokker 70 is a Dutch-built, twin-engine regional jet airliner designed for short- to medium-haul routes, widely used in Europe during the 1990s and 2000s.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca847e53a88190a60eed7e02257f10 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9965e7b881909df98e933db38092 |
completed | April 1, 2026, 10:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d152a014a48190925d52967e1fbffe |
completed | April 4, 2026, 6:04 p.m. |
Created at: March 30, 2026, 8:03 p.m.