Triple
T21836997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M923A1 |
E539144
|
entity |
| Predicate | hasCargoCover |
P10512
|
FINISHED |
| Object | removable canvas cover |
—
|
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: removable canvas cover | Statement: [M923A1, hasCargoCover, removable canvas cover]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCargoCover Context triple: [M923A1, hasCargoCover, removable canvas cover]
-
A.
hasCargoAccess
Indicates that an entity has the ability or permission to access a designated cargo area or its contents.
-
B.
hasCoverType
chosen
Indicates that one entity possesses or is associated with a specific type or category of cover.
-
C.
hasCoverFeature
Indicates that one entity serves as a prominent or featured element on the cover of another entity (such as a publication, product, or media item).
-
D.
hasCargoDoorVariant
Indicates that one entity is a specific cargo-door-equipped version or configuration variant of another entity.
-
E.
hasOpenCoverCondition
Indicates that a mathematical object satisfies the open cover condition, meaning every open cover of it admits a suitable refinement or subcover meeting the specified requirement.
- 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.