Triple

T12832200
Position Surface form Disambiguated ID Type / Status
Subject Paris of India E306815 entity
Predicate comparativeReason P51217 FINISHED
Object beauty and elegance of the cityscape 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: beauty and elegance of the cityscape | Statement: [Paris of India, comparativeReason, beauty and elegance of the cityscape]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: comparativeReason
Context triple: [Paris of India, comparativeReason, beauty and elegance of the cityscape]
  • A. similarityReason
    Indicates that there is an identified basis or explanation for why two entities are considered similar.
  • B. comparisonAspect chosen
    Indicates that two or more entities are being compared specifically with respect to a particular shared attribute or dimension.
  • C. comparisonType
    Indicates the specific kind of comparison being made between two or more values or entities (e.g., equality, inequality, ordering, or similarity).
  • D. notableComparison
    Indicates that one entity is being compared to another in a way that is especially significant, remarkable, or worthy of note.
  • E. selectionReason
    Indicates the reason or justification for choosing or selecting one entity over alternatives.
  • 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_69d7bdf52b94819096d6f0ba4ab50a98 completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d9714208f881908f7f8a921362909a completed April 10, 2026, 9:53 p.m.
PD Predicate disambiguation batch_69d96fa08cd481909a946046ba63809f completed April 10, 2026, 9:46 p.m.
Created at: April 9, 2026, 5:34 p.m.