Triple
T18279699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M561 tractor unit |
E437831
|
entity |
| Predicate | operatorCapacity |
P131149
|
FINISHED |
| Object | driver |
—
|
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: driver | Statement: [M561 tractor unit, operatorCapacity, driver]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatorCapacity Context triple: [M561 tractor unit, operatorCapacity, driver]
-
A.
smsCapacity
Indicates the maximum number of SMS messages that can be stored, sent, or handled within a given system or context.
-
B.
offersCapacityRange
Indicates that an entity provides or makes available a service, product, or resource whose capacity is specified as a range between a minimum and maximum value.
-
C.
launcherCapacity
Indicates the maximum number or size of items that a launcher is designed to hold or deploy.
-
D.
capacityRecord
Indicates a recorded measure of how much of a resource, space, or system is available or can be utilized at a given time.
-
E.
unitCapacity
Indicates the maximum quantity or load that a single unit is designed or allowed to hold, process, or accommodate.
- F. None of above. chosen
Provenance (4 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_69d8b914530c8190b4474d862a2b2a1b |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e50054d1dc8190b31d02f617256e9d |
completed | April 19, 2026, 4:18 p.m. |
| PD | Predicate disambiguation | batch_69e44fd81c788190b08c6be3b07a08c5 |
completed | April 19, 2026, 3:45 a.m. |
| PDg | Predicate description generation | batch_69e451a0ba208190a5fe92832a8f7a49 |
completed | April 19, 2026, 3:53 a.m. |
Created at: April 10, 2026, 10:34 a.m.