Triple
T26007308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | INX |
E646793
|
entity |
| Predicate | commonlyExportedFrom |
P173200
|
FINISHED |
| Object | Adobe InDesign CS |
—
|
NE NERFINISHED |
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: Adobe InDesign CS | Statement: [INX, commonlyExportedFrom, Adobe InDesign CS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonlyExportedFrom Context triple: [INX, commonlyExportedFrom, Adobe InDesign CS]
-
A.
exportedFrom
Indicates that something has been sent out or shipped from a particular place, source, or origin to another location.
-
B.
exportedVia
Indicates that something is sent out or made available to an external destination through a specified medium, channel, or mechanism.
-
C.
exportedTo
Indicates that goods, services, or resources are sent out from one entity or region to another for trade or sale.
-
D.
otherExports
Indicates that an entity exports additional goods or services beyond its primary or specifically listed export categories.
-
E.
exportedAs
Indicates that something is made available or delivered to an external destination under a specified name, format, or representation.
- 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_69e77e89d5848190b54352cdb74f6029 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6b342499c8190b85009a3f0f179e4 |
completed | May 3, 2026, 2:30 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
| PDg | Predicate description generation | batch_69f6b2a31e008190aacef03c2ebe5787 |
completed | May 3, 2026, 2:27 a.m. |
Created at: April 22, 2026, 9:01 a.m.