Triple
T22438968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bond Arms Ranger |
E554701
|
entity |
| Predicate | intendedCarryMethod |
P148193
|
FINISHED |
| Object | belt holster |
—
|
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: belt holster | Statement: [Bond Arms Ranger, intendedCarryMethod, belt holster]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedCarryMethod Context triple: [Bond Arms Ranger, intendedCarryMethod, belt holster]
-
A.
carriedBy
Indicates that one entity is physically supported and transported by another entity.
-
B.
mobilizationMethod
Indicates the method or process by which resources, people, or assets are organized and activated for a particular purpose or operation.
-
C.
transportedWith
Indicates that one entity was moved or carried together with another entity as part of the same transport event.
-
D.
transportAccessType
Indicates the type or mode of transportation access available or used in a given context.
-
E.
transportAssumption
Indicates an assumption that something can be transported or carried from one place or context to another.
- 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_69e11e5010e48190ae1e9c9db9697637 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15ae01bd08190aee5141f4c0848bc |
completed | April 29, 2026, 1:12 a.m. |
| PD | Predicate disambiguation | batch_69e898a327948190beee5e168006a0a7 |
completed | April 22, 2026, 9:45 a.m. |
| PDg | Predicate description generation | batch_69e8aa39e3388190b659d59948ebf3e6 |
completed | April 22, 2026, 11 a.m. |
Created at: April 16, 2026, 8:47 p.m.