Triple
T7492050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | crawler-transporter |
E177027
|
entity |
| Predicate | speedUnloaded |
P13562
|
FINISHED |
| Object | about 2 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: about 2 miles per hour | Statement: [crawler-transporter, speedUnloaded, about 2 miles per hour]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: speedUnloaded Context triple: [crawler-transporter, speedUnloaded, about 2 miles per hour]
-
A.
speed
chosen
Indicates the rate at which an entity moves or changes position over time.
-
B.
speedAchieved
Indicates that a particular speed has been reached or attained by an entity during an event or action.
-
C.
maxSpeed
Indicates the greatest possible speed at which an entity can move or operate under specified conditions.
-
D.
canReduceSpeedTo
Indicates that an entity has the capability to lower its speed to a specified level or threshold.
-
E.
speedClass
Indicates the categorical speed level or range assigned to an entity based on how fast it moves or operates.
- 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_69c69f2583808190bd1a4936c42a5815 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f81b431481908214b69c6c8d83bc |
completed | March 27, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69c6f4d266d88190982cf5d2ee2e9564 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:43 p.m.