Triple
T35259974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pandataria |
E1018342
|
entity |
| Predicate | eraOfMainUseAsExile |
P57102
|
FINISHED |
| Object | 1st 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: 1st century BCE | Statement: [Pandataria, eraOfMainUseAsExile, 1st century BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eraOfMainUseAsExile Context triple: [Pandataria, eraOfMainUseAsExile, 1st century BCE]
-
A.
eraOfPrimaryMilitaryUse
Indicates the historical time period during which the subject was primarily used for military purposes.
-
B.
usedInExile
Indicates that something (such as a method, name, or identity) is employed or applied while an entity is in a state of exile.
-
C.
equippedFor
Indicates that one entity is suitably provided with the necessary tools, features, or capabilities to perform a particular function or handle a specific situation for another entity or purpose.
-
D.
eraOfOperation
Indicates the time period or span of years during which an entity was active or in operation.
-
E.
eraUsedIn
chosen
Indicates that something (such as a method, standard, or practice) was in active use during a specified historical or temporal era.
- 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_69f76de4be5c8190a51705c07612cac8 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7b0e5744c8190a22c1e1d6fcfa466 |
completed | May 3, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f7ab70d034819080295628497d8582 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:02 p.m.