Triple
T23758011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mauryan mining administration |
E587172
|
entity |
| Predicate | appliesToCentury |
P56280
|
FINISHED |
| Object | 4th century BCE |
—
|
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: 4th century BCE | Statement: [Mauryan mining administration, appliesToCentury, 4th century BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToCentury Context triple: [Mauryan mining administration, appliesToCentury, 4th century BCE]
-
A.
usedInCentury
Indicates that something (such as an object, practice, or concept) was in use during a specified century.
-
B.
associatedWithCentury
chosen
Indicates that something has a relevant connection or linkage to a particular century, such as occurring in, belonging to, or being characteristic of that time period.
-
C.
endedInCentury
Indicates that an event, period, or process concluded during a specified century.
-
D.
claimedInCentury
Indicates that a claim or assertion was made or recorded during a specified century.
-
E.
declaredInCentury
Indicates that something (such as an event, work, or concept) was formally declared or proclaimed during a specified century.
- 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_69e2490a0eec81908cdef8a862828d7a |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1bdad46888190b438b22985838640 |
completed | April 29, 2026, 8:13 a.m. |
| PD | Predicate disambiguation | batch_69f155f79e34819080f9ddb972b34deb |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:14 p.m.