Triple
T27490010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vrishni clan |
E693852
|
entity |
| Predicate | hasLegendaryCapital |
P160636
|
FINISHED |
| Object | Mathura |
—
|
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: Mathura | Statement: [Vrishni clan, hasLegendaryCapital, Mathura]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLegendaryCapital Context triple: [Vrishni clan, hasLegendaryCapital, Mathura]
-
A.
legendaryCapital
chosen
Indicates that a location serves as the capital city within legend, myth, or folklore rather than in historical or political reality.
-
B.
hasCapitalFeature
Indicates that one entity possesses or is characterized by a primary or most important feature represented by the other entity.
-
C.
hasCapitalNamedAfterRole
Indicates that an entity’s capital city is named after a role, title, or position rather than a specific individual or other naming basis.
-
D.
hasLegendaryPlayer
Indicates that an entity (such as a team, club, or organization) is associated with at least one player recognized as legendary.
-
E.
hasCultOrLegend
Indicates that an entity is associated with, or is the subject of, a cult, myth, or legendary tradition.
- 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_69ef5382b9648190be0b1ef2ad5d043c |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f6db1f3ec48190a82e7d893d3c76ba |
completed | May 3, 2026, 5:20 a.m. |
| PD | Predicate disambiguation | batch_69f6d82adfa481908a5e196d2e18c73f |
completed | May 3, 2026, 5:07 a.m. |
Created at: April 27, 2026, 1:04 p.m.