Triple
T24928903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adobe Dynamic Link |
E618933
|
entity |
| Predicate | laterBundledWith |
P56452
|
FINISHED |
| Object | Adobe Creative Cloud |
—
|
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 Creative Cloud | Statement: [Adobe Dynamic Link, laterBundledWith, Adobe Creative Cloud]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterBundledWith Context triple: [Adobe Dynamic Link, laterBundledWith, Adobe Creative Cloud]
-
A.
laterComplementedBy
Indicates that an earlier entity is subsequently supplemented, enhanced, or completed by a later entity.
-
B.
laterIncludedOn
chosen
Indicates that one entity was added to, incorporated into, or featured on another entity at a subsequent time.
-
C.
laterCompiledAs
Indicates that one work, version, or material was subsequently gathered, edited, or assembled into another compiled work.
-
D.
laterUsedBy
Indicates that something is subsequently utilized or employed by a specified entity at a later time.
-
E.
alsoComposedWith
Indicates that something is created or formed together with one or more additional components, highlighting a joint or complementary composition relationship.
- 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_69e2fab9edd88190b86004a78a28bc20 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f55e519978819087a1676564a74630 |
completed | May 2, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69f4a0edd10c81908a052ab864d57c54 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 18, 2026, 5:29 a.m.