Triple
T13777498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roland TR-08 |
E331045
|
entity |
| Predicate | hasPortability |
P57891
|
FINISHED |
| Object | portable |
—
|
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: portable | Statement: [Roland TR-08, hasPortability, portable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPortability Context triple: [Roland TR-08, hasPortability, portable]
-
A.
isPortable
chosen
Indicates that an object can be easily moved or carried from one place to another without significant effort or setup.
-
B.
portabilityMethod
Indicates the method or mechanism by which something can be transferred or moved from one context, system, or location to another.
-
C.
portabilityConcern
Indicates a relationship where an entity is associated with issues, risks, or considerations about how easily it can be moved, transferred, or used across different environments or contexts.
-
D.
isPortableComparedTo
Indicates that one entity can be moved, carried, or transported more easily than another entity.
-
E.
isLessPortableThan
Indicates that one entity is more difficult to move, carry, or transport than another entity.
- 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_69d81c583b0081909e408a17db517a21 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de0239cbfc81909064ac2457fdfff5 |
completed | April 14, 2026, 9 a.m. |
| PD | Predicate disambiguation | batch_69dbbe97846c819093b00ea117b64e0d |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 10:10 p.m.