Triple
T5074362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Messerschmitt P.1101 |
E114356
|
entity |
| Predicate | intendedSpeedClass |
P9902
|
FINISHED |
| Object | high-subsonic |
—
|
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: high-subsonic | Statement: [Messerschmitt P.1101, intendedSpeedClass, high-subsonic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedSpeedClass Context triple: [Messerschmitt P.1101, intendedSpeedClass, high-subsonic]
-
A.
speedClass
chosen
Indicates the categorical speed level or range assigned to an entity based on how fast it moves or operates.
-
B.
recommendedSpeed
Indicates the speed that is advised or suggested as appropriate under given conditions, rather than required or actual speed.
-
C.
speedAchieved
Indicates that a particular speed has been reached or attained by an entity during an event or action.
-
D.
maxSpeed
Indicates the greatest possible speed at which an entity can move or operate under specified conditions.
-
E.
speedLimitCharacteristic
Indicates that an entity has a specific speed limit property or constraint associated with it.
- 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_69bd443cf28c8190ad371d603563dbdd |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd74d0be1c819081b26235fe602a30 |
completed | March 20, 2026, 4:24 p.m. |
| PD | Predicate disambiguation | batch_69bd7157fe608190b4515d56fdd0a616 |
completed | March 20, 2026, 4:10 p.m. |
Created at: March 20, 2026, 1:39 p.m.