Triple
T9989571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Urdu literature |
E196850
|
entity |
| Predicate | reflectsAspect |
P61123
|
FINISHED |
| Object | South Asian culture |
—
|
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: South Asian culture | Statement: [Urdu literature, reflectsAspect, South Asian culture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reflectsAspect Context triple: [Urdu literature, reflectsAspect, South Asian culture]
-
A.
refersToAspect
Indicates that one entity specifically references or points to a particular aspect, feature, or component of another entity.
-
B.
coversAspect
chosen
Indicates that one entity addresses, includes, or deals with a particular aspect or facet of another entity or topic.
-
C.
onAspect
Indicates that one entity is positioned on a particular side, surface, or facet of another entity.
-
D.
symbolicAspect
Indicates that one entity functions as a symbol or emblem that represents, expresses, or conveys a particular meaning, quality, or concept of another entity.
-
E.
typeOfAspect
Indicates that one aspect is a specific kind or category of another, more general aspect.
- 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_69ca82f1678c819093d06320a05f16a4 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdc79f3df08190ab3094ad1cd5490f |
completed | April 2, 2026, 1:34 a.m. |
| PD | Predicate disambiguation | batch_69cd1da07db88190945bcdab3ca82e71 |
completed | April 1, 2026, 1:29 p.m. |
Created at: March 30, 2026, 8:50 p.m.