Triple
T2877257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kumbhalgarh Fort |
E56906
|
entity |
| Predicate | wallFeature |
P43476
|
FINISHED |
| Object | among the longest continuous walls in the world |
—
|
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: among the longest continuous walls in the world | Statement: [Kumbhalgarh Fort, wallFeature, among the longest continuous walls in the world]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wallFeature Context triple: [Kumbhalgarh Fort, wallFeature, among the longest continuous walls in the world]
-
A.
wallMaterial
Indicates that one entity is the material from which a wall or walls of another entity are constructed.
-
B.
wallTreatment
Indicates how a wall is finished, covered, or treated in terms of its surface appearance or protective coating.
-
C.
roofFeature
Indicates that one entity is a feature, element, or characteristic that is part of or associated with a roof.
-
D.
hasWallShape
Indicates that an entity possesses a wall whose form or outline matches a specified geometric or structural shape.
-
E.
hasWallType
Indicates the specific kind or classification of wall associated with an entity.
- F. None of above. chosen
Provenance (4 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_69ab4a4ced288190ab6d3e062d10f7f6 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abe007329c8190b0bc1851c7307124 |
completed | March 7, 2026, 8:21 a.m. |
| PD | Predicate disambiguation | batch_69abdd142e4c8190b424cb0c5ff40d04 |
completed | March 7, 2026, 8:08 a.m. |
| PDg | Predicate description generation | batch_69abde2cdcc48190827195d3ae70aa19 |
completed | March 7, 2026, 8:13 a.m. |
Created at: March 6, 2026, 10:03 p.m.