Triple
T22048569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Narasimha Jayanti |
E544824
|
entity |
| Predicate | commonOffering |
P103123
|
FINISHED |
| Object | flowers |
—
|
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: flowers | Statement: [Narasimha Jayanti, commonOffering, flowers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonOffering Context triple: [Narasimha Jayanti, commonOffering, flowers]
-
A.
associatedOffering
Indicates a relationship where one offering is linked or connected to another offering as related or contextually relevant.
-
B.
typicalOfferings
chosen
Indicates that one entity commonly provides, includes, or features another as part of its standard or usual set of offerings.
-
C.
offeringType
Indicates the category or nature of what is being offered in a transaction or interaction (e.g., product, service, or other type of offering).
-
D.
offeredService
Indicates that one entity has provided or made available a service to another entity.
-
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_69e11e32445c8190ab97089b48a130bb |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f1283191e48190b4ddc84138243327 |
completed | April 28, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69e6f643ca74819083e8ab78e843f243 |
completed | April 21, 2026, 4 a.m. |
Created at: April 16, 2026, 8:26 p.m.