Triple
T21059404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Molossian Kingdom |
E518810
|
entity |
| Predicate | dissolvedCentury |
P98054
|
FINISHED |
| Object | 3rd century BC |
—
|
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: 3rd century BC | Statement: [Molossian Kingdom, dissolvedCentury, 3rd century BC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dissolvedCentury Context triple: [Molossian Kingdom, dissolvedCentury, 3rd century BC]
-
A.
discoveredInCentury
Indicates that an entity was discovered during a specific century.
-
B.
century
Indicates that an entity is associated with, occurs in, or belongs to a particular 100-year time period.
-
C.
disappearedByCentury
chosen
Indicates the century during which an entity ceased to exist, vanished, or was no longer present.
-
D.
revealedInCentury
Indicates that something became known, disclosed, or publicly revealed during a specified century.
-
E.
lostCentury
Indicates that a particular century or era has been forgotten, obscured, or is missing from records or collective knowledge.
- 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_69e0b5053ac48190921529544959e906 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fd842e8881909f4ffc4c43b7fa9f |
completed | April 21, 2026, 4:31 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf9d71881908cd85dfc37db93ca |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:37 p.m.