Triple
T26892858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mahasthangarh |
E677821
|
entity |
| Predicate | citadelArea |
P161304
|
FINISHED |
| Object | approximately 185 hectares |
—
|
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: approximately 185 hectares | Statement: [Mahasthangarh, citadelArea, approximately 185 hectares]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: citadelArea Context triple: [Mahasthangarh, citadelArea, approximately 185 hectares]
-
A.
citadelAlsoCalled
Indicates that a citadel is known or referred to by an alternative name or alias.
-
B.
citadelDimensions
chosen
Indicates the physical measurements or size specifications associated with a citadel.
-
C.
roleInCitadel
Indicates the specific function, position, or responsibility an entity holds within a citadel or fortified complex.
-
D.
modernAreaCorrespondsTo
Indicates that a historical or former area is associated with, or has its equivalent in, a specified modern geographic or administrative area.
-
E.
wasCitadelOf
Indicates that a place previously served as the main fortified stronghold or central defensive structure for another entity.
- 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_69eee9befee48190a26f214faa867be7 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f61fd623bc819091df736cf3419b99 |
completed | May 2, 2026, 4:01 p.m. |
| PD | Predicate disambiguation | batch_69f61b3d23f481908dfec27adace900a |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 5:46 a.m.