Triple
T25426846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RTMP |
E637135
|
entity |
| Predicate | wasProprietaryTo |
P59297
|
FINISHED |
| Object | Adobe Systems |
—
|
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 Systems | Statement: [RTMP, wasProprietaryTo, Adobe Systems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasProprietaryTo Context triple: [RTMP, wasProprietaryTo, Adobe Systems]
-
A.
wasProprietaryUntil
Indicates that something was owned or controlled as proprietary (not publicly available or open) up to a specified point in time.
-
B.
hasProprietaryStatus
Indicates that something is owned, controlled, or protected as proprietary rather than being public or freely available.
-
C.
isProprietaryAlternativeTo
Indicates that one entity is a closed-source or commercially restricted substitute for another, typically offering similar functionality under proprietary terms.
-
D.
previouslyPossessedBy
chosen
Indicates that an entity was owned or possessed by another entity at some time in the past, but is not necessarily possessed by that entity now.
-
E.
ownedProperty
Indicates that one entity possesses legal ownership or control over another entity as property.
- 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_69e75db58a1c8190891b9ff7c2f8414e |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f6c0a1808190a7d577f22a2f31d1 |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f45d0dbc8c8190beecce679fce90a4 |
completed | May 1, 2026, 7:58 a.m. |
Created at: April 21, 2026, 1:57 p.m.