Triple
T20938049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khandavaprastha |
E515637
|
entity |
| Predicate | formerCondition |
P30469
|
FINISHED |
| Object | forested wilderness |
—
|
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: forested wilderness | Statement: [Khandavaprastha, formerCondition, forested wilderness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerCondition Context triple: [Khandavaprastha, formerCondition, forested wilderness]
-
A.
presentCondition
Indicates that an entity currently has or exhibits a particular state, situation, or condition.
-
B.
formerState
chosen
Indicates that an entity previously held the status or condition of a particular state but no longer does so.
-
C.
usedCondition
Indicates that one entity is employed or applied under a particular state, requirement, or circumstance defined by another entity.
-
D.
formerFlag
Indicates that an entity previously served as a flag of another entity but no longer holds that status.
-
E.
formerType
Indicates that one entity previously had a certain type, role, or classification but no longer does.
- 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_69e0b4fc13408190b06868df03c5c29b |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6f9534cd48190a86665fb1df6b077 |
completed | April 21, 2026, 4:13 a.m. |
| PD | Predicate disambiguation | batch_69e5c9af1fe08190953366a466950140 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:50 p.m.