Triple
T21705778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cairo Station |
E535767
|
entity |
| Predicate | mainCharacter |
P1183
|
FINISHED |
| Object | Hanuma |
—
|
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: Hanuma | Statement: [Cairo Station, mainCharacter, Hanuma]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hanuma Context triple: [Cairo Station, mainCharacter, Hanuma]
-
A.
Hanuman
chosen
Hanuman is a revered Hindu deity known for his immense strength, unwavering devotion to Lord Rama, and central role in the epic Ramayana.
-
B.
Lakshmana
Lakshmana is a devoted younger brother of Rama in the Hindu epic Ramayana, renowned for his unwavering loyalty, courage, and selfless service.
-
C.
Anjaneya
Anjaneya is another name for the Hindu deity Hanuman, revered as a symbol of strength, devotion, and selfless service.
-
D.
Hanuma Vihari
Hanuma Vihari is an Indian cricketer and technically sound middle-order batsman who has represented India in Test matches and played domestic cricket with distinction.
-
E.
Lakshmana Kumara
Lakshmana Kumara is a relatively obscure figure in the Mahabharata, known primarily as the nephew of the Kuru teacher Kripa.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0c46b44c0819088ab883ebd44e0e8 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69efb52f64c48190b5d59561999e922f |
completed | April 27, 2026, 7:12 p.m. |
Created at: April 16, 2026, 6:46 p.m.