Triple
T36978663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pilot Rexgrip |
E914763
|
entity |
| Predicate | isRefillable |
P105529
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Pilot Rexgrip, isRefillable, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRefillable Context triple: [Pilot Rexgrip, isRefillable, true]
-
A.
refillsAfter
Indicates that one entity replenishes or fills another entity following a specified event, time, or condition.
-
B.
canBeReconstituted
Indicates that something has the capacity to be restored or returned to a prior or functional state, typically after being separated, dissolved, or broken down.
-
C.
isReusableCapsule
chosen
Indicates that a capsule is designed to be used multiple times rather than being discarded after a single use.
-
D.
isTypicallyFilledWith
Indicates that one entity is commonly or usually occupied, loaded, or contained by another entity.
-
E.
rechargeable
Indicates that an entity can have its stored energy replenished, typically by being connected to a power source, and thus can be used repeatedly rather than discarded after a single use.
- 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_69f76e8d13b4819089af24a47ce092fc |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb154c0fe08190a2e41e7a29b6055f |
completed | May 6, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_69f9fecc005c8190be082a8689193745 |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:14 p.m.