Triple
T26007312
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | INX |
E646793
|
entity |
| Predicate | canBeImportedInto |
P127767
|
FINISHED |
| Object | newer versions of Adobe InDesign |
—
|
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: newer versions of Adobe InDesign | Statement: [INX, canBeImportedInto, newer versions of Adobe InDesign]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeImportedInto Context triple: [INX, canBeImportedInto, newer versions of Adobe InDesign]
-
A.
importedWith
Indicates that one entity was brought into a system, context, or location together with or as part of another entity during an import process.
-
B.
canBeAddedTo
Indicates that one entity is capable of being combined or incorporated with another entity, typically without conflict or incompatibility.
-
C.
canBeLoadedBy
chosen
Indicates that one entity is capable of being loaded, initialized, or brought into use by another entity.
-
D.
exportedTo
Indicates that goods, services, or resources are sent out from one entity or region to another for trade or sale.
-
E.
supportsImportExport
Indicates that one entity provides functionality for importing and exporting data or resources to and from 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_69e77e89d5848190b54352cdb74f6029 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 22, 2026, 9:01 a.m.