Triple
T26405708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adobe Experience Manager |
E663824
|
entity |
| Predicate | usesRepositoryType |
P34278
|
FINISHED |
| Object | Java Content Repository |
—
|
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: Java Content Repository | Statement: [Adobe Experience Manager, usesRepositoryType, Java Content Repository]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesRepositoryType Context triple: [Adobe Experience Manager, usesRepositoryType, Java Content Repository]
-
A.
usesRepository
chosen
Indicates that one entity relies on, accesses, or interacts with a particular repository as a resource or data source.
-
B.
usesCollection
Indicates that one entity makes use of, depends on, or operates with a particular collection of items or resources.
-
C.
usedOrganActionType
Indicates that an action involves or is performed using a specific organ or type of organ function.
-
D.
usedByInstitutionType
Indicates that something (such as a resource, tool, or service) is utilized or employed by a particular type or category of institution.
-
E.
usageType
Indicates the specific manner, purpose, or context in which something is used or intended to be used.
- 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_69ee883931888190901be96d75ee23cc |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f610f87374819084279ca5c2f3d32f |
completed | May 2, 2026, 2:58 p.m. |
| PD | Predicate disambiguation | batch_69f60b89cc048190a9feb24466006be0 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 26, 2026, 11:34 p.m.