Triple
T10793786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Y-20 |
E254650
|
entity |
| Predicate | intendedPayloadType |
P8440
|
FINISHED |
| Object | heavy equipment |
—
|
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: heavy equipment | Statement: [Y-20, intendedPayloadType, heavy equipment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedPayloadType Context triple: [Y-20, intendedPayloadType, heavy equipment]
-
A.
payloadType
chosen
Indicates the kind or category of payload associated with or carried by an entity or action.
-
B.
plannedPayload
Indicates that an entity is designated or scheduled to be carried, delivered, or transported as part of a planned operation or mission.
-
C.
intendedReceiver
Indicates that one entity is the target or designated recipient of something (such as a message, item, or action) originating from another entity.
-
D.
usesPayload
Indicates that one entity employs or utilizes another entity as its payload in performing an action or function.
-
E.
compatiblePayload
Indicates that one entity can be safely or effectively used as the payload of another entity without conflict or required modification.
- 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_69d6aa609f008190a294200aefcb7bd5 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d732f878648190be5e25c56a7511cf |
completed | April 9, 2026, 5:02 a.m. |
| PD | Predicate disambiguation | batch_69d6f316940c819092a96c429629fdef |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:17 p.m.