Triple
T3560755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Concorde G-BOAC |
E75330
|
entity |
| Predicate | typicalServiceSpeedClass |
P9902
|
FINISHED |
| Object | Mach 2-class |
—
|
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: Mach 2-class | Statement: [Concorde G-BOAC, typicalServiceSpeedClass, Mach 2-class]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalServiceSpeedClass Context triple: [Concorde G-BOAC, typicalServiceSpeedClass, Mach 2-class]
-
A.
speedClass
chosen
Indicates the categorical speed level or range assigned to an entity based on how fast it moves or operates.
-
B.
dataRate
Indicates the rate at which data is transmitted, processed, or transferred between entities over a given time interval.
-
C.
hasAverageSurfaceSpeed
Indicates the typical or mean speed at which something moves across a surface over a given period or distance.
-
D.
typicalServiceRequirement
Indicates that a certain condition, resource, or specification is normally needed or expected for a service to be properly provided or operated.
-
E.
serviceClass
Indicates the classification or category of service associated with or provided by an entity in the relationship.
- 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_69ad85d45090819086f34fb85d850a1e |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc08ac1b0819082021ecdd0061dc3 |
completed | March 8, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69adb834779081908468e182d5f6cf02 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:21 p.m.