Triple
T26533622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Agneepath (1990 film) |
E670882
|
entity |
| Predicate | featuresPoem |
P188413
|
FINISHED |
| Object | "Agneepath" |
—
|
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: "Agneepath" | Statement: [Agneepath (1990 film), featuresPoem, "Agneepath"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresPoem Context triple: [Agneepath (1990 film), featuresPoem, "Agneepath"]
-
A.
hasFeatureInPoem
Indicates that a poem includes or is characterized by a particular feature, element, or attribute.
-
B.
poem
Indicates that one entity is a poem created, authored, or associated with another entity.
-
C.
poetryFunction
Indicates that one entity serves a particular role, purpose, or function within the domain of poetry for another entity.
-
D.
poeticStructure
Indicates a relationship where one entity defines, embodies, or specifies the formal poetic organization (such as meter, rhyme scheme, or stanza pattern) used by another entity.
-
E.
literaryFeature
Indicates a relationship where something possesses or exhibits a characteristic, device, or stylistic element used in literature.
- F. None of above. chosen
Provenance (4 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_69eeb31ea1e08190b9ff43cf9bc25bf8 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69fba789c1188190973a919bfe2871f3 |
completed | May 6, 2026, 8:41 p.m. |
Created at: April 27, 2026, 1:37 a.m.