Triple
T21837079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M927 |
E539146
|
entity |
| Predicate | designedToTransport |
P99081
|
FINISHED |
| Object | troops |
—
|
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: troops | Statement: [M927, designedToTransport, troops]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedToTransport Context triple: [M927, designedToTransport, troops]
-
A.
commonlyTransportedIn
Indicates that something is usually carried, moved, or conveyed using a particular vehicle, container, or mode of transport.
-
B.
canBeTransportedOver
Indicates that one entity is capable of being moved or carried across, along, or by means of another entity or medium.
-
C.
transportUnit
chosen
Indicates a relationship where one entity serves as a means or unit for transporting another entity from one place to another.
-
D.
designedCargoCapacity
Indicates the maximum amount of cargo an object (such as a vehicle or container) was originally engineered or specified to carry.
-
E.
transportedWith
Indicates that one entity was moved or carried together with another entity as part of the same transport event.
- 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_69e0c475cda88190987d08f23caebdc1 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f0a7a890208190a902184e60194e1c |
completed | April 28, 2026, 12:27 p.m. |
| PD | Predicate disambiguation | batch_69e6be8c14748190bdcc44a14d50bea4 |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 6:55 p.m.