Triple
T7122898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ektara |
E165988
|
entity |
| Predicate | portability |
P57891
|
FINISHED |
| Object | high |
—
|
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: high | Statement: [ektara, portability, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: portability Context triple: [ektara, portability, high]
-
A.
isPortable
chosen
Indicates that an object can be easily moved or carried from one place to another without significant effort or setup.
-
B.
isPortableComparedTo
Indicates that one entity can be moved, carried, or transported more easily than another entity.
-
C.
isLessPortableThan
Indicates that one entity is more difficult to move, carry, or transport than another entity.
-
D.
porte
Indicates that an entity carries, wears, or bears another entity (such as an object, attribute, or characteristic).
-
E.
port
Indicates a relationship where one entity serves as a harbor, access point, or interface through which another entity can enter, exit, or connect.
- 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_69c6888350588190870cd552b427a1cd |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e6493fd88190b0c066a2ad74917c |
completed | March 27, 2026, 8:19 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c7289881909f3b533c384f9ed4 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:44 p.m.