Triple
T12691524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iron Pillar of Delhi |
E303214
|
entity |
| Predicate | baseFeature |
P106366
|
FINISHED |
| Object | buried below ground level |
—
|
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: buried below ground level | Statement: [Iron Pillar of Delhi, baseFeature, buried below ground level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: baseFeature Context triple: [Iron Pillar of Delhi, baseFeature, buried below ground level]
-
A.
baseType
Indicates that one entity serves as the underlying or parent type from which another entity is derived or specialized.
-
B.
isFeatureBased
Indicates that one entity is derived from, determined by, or constructed using the characteristics or attributes of another entity.
-
C.
baseStandard
Indicates that one entity serves as the foundational or reference standard upon which another entity is defined, measured, or evaluated.
-
D.
featureType
Indicates the specific kind or category of feature that characterizes or distinguishes an entity.
-
E.
targetFeature
Indicates that one entity is the specific feature, attribute, or characteristic that another entity is directed toward, focused on, or intended to affect.
- 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_69d7bdef90d48190b46b88270e780946 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d962a32c6481908ddaddae4ea267bf |
completed | April 10, 2026, 8:50 p.m. |
| PD | Predicate disambiguation | batch_69d960be63f081908a5ef5ef17a311bf |
completed | April 10, 2026, 8:42 p.m. |
| PDg | Predicate description generation | batch_69d96297b81c819081ad1432dc5f15f4 |
completed | April 10, 2026, 8:50 p.m. |
Created at: April 9, 2026, 5:22 p.m.