Triple
T26925592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Classical period of ancient India |
E677770
|
entity |
| Predicate | hasCorePhase |
P197351
|
FINISHED |
| Object | Gupta period |
—
|
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: Gupta period | Statement: [Classical period of ancient India, hasCorePhase, Gupta period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCorePhase Context triple: [Classical period of ancient India, hasCorePhase, Gupta period]
-
A.
hasCore
Indicates that one entity possesses, contains, or is built around a central or most essential component represented by another entity.
-
B.
hasCoreState
Indicates that an entity possesses or is associated with a fundamental or primary state that defines its core condition or behavior.
-
C.
hasCoreWork
Indicates that an entity possesses or is associated with a primary, central, or most essential piece of work or activity.
-
D.
hasCoreUnit
Indicates that an entity includes or is composed around a primary, central, or fundamental unit.
-
E.
hasCoreStrategy
Indicates that an entity possesses or is associated with a primary, central, or foundational strategy guiding its actions or decisions.
- 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_69eee9bdebc48190ba90a12a63e09c73 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69fe8ddf70e48190a917eb9e8f7b6966 |
completed | May 9, 2026, 1:29 a.m. |
| PD | Predicate disambiguation | batch_69fe87ef94dc81909bb00ec8d6de9bcd |
completed | May 9, 2026, 1:03 a.m. |
| PDg | Predicate description generation | batch_69fe8dde8d008190b03dc0f97618073c |
completed | May 9, 2026, 1:29 a.m. |
Created at: April 27, 2026, 6:09 a.m.