Triple
T35790166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kenneth Arnold |
E1034671
|
entity |
| Predicate | speedOfObjectsReported |
P13562
|
FINISHED |
| Object | approximately 1,200 miles per hour |
—
|
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: approximately 1,200 miles per hour | Statement: [Kenneth Arnold, speedOfObjectsReported, approximately 1,200 miles per hour]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: speedOfObjectsReported Context triple: [Kenneth Arnold, speedOfObjectsReported, approximately 1,200 miles per hour]
-
A.
speedSupervision
Indicates a relationship where an entity monitors, controls, or enforces limits on the speed of another entity or process.
-
B.
speedMeasurementMethod
Indicates the method or technique used to measure the speed of an entity or process.
-
C.
speedAchieved
Indicates that a particular speed has been reached or attained by an entity during an event or action.
-
D.
speed
chosen
Indicates the rate at which an entity moves or changes position over time.
-
E.
reportedGroupVelocity
Indicates that a group’s velocity has been measured or estimated and formally reported as a value associated with that group.
- 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_69f76e1575908190aaa306d843b41c14 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a22e0ff88190989a5df84fca968b |
completed | May 3, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69f7a070e23881909a233370acb57384 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:06 p.m.