Triple
T1500164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Omniture |
E29776
|
entity |
| Predicate | offeredFeature |
P9404
|
FINISHED |
| Object | real-time reporting |
—
|
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: real-time reporting | Statement: [Omniture, offeredFeature, real-time reporting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offeredFeature Context triple: [Omniture, offeredFeature, real-time reporting]
-
A.
offersFeature
chosen
Indicates that one entity provides or makes available a particular feature or capability to another entity.
-
B.
offeredService
Indicates that one entity has provided or made available a service to another entity.
-
C.
offersProgram
Indicates that an entity provides or makes available a specific program (such as a course, curriculum, or initiative).
-
D.
associatedOffering
Indicates a relationship where one offering is linked or connected to another offering as related or contextually relevant.
-
E.
offering
Indicates that one entity presents or provides something to another entity, typically as a gift, contribution, or proposal.
- 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_69a498dba1d8819093b46a3a8d2485f1 |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c6f2d7f881909188a3e5614335cd |
completed | March 1, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69a4c48a8cf48190a6ebf8d44a608a06 |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8:12 p.m.