Triple
T389494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Assyrians |
E8850
|
entity |
| Predicate | historicalContinuityWith |
P8384
|
FINISHED |
| Object | ancient Assyrians |
—
|
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: ancient Assyrians | Statement: [Assyrians, historicalContinuityWith, ancient Assyrians]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalContinuityWith Context triple: [Assyrians, historicalContinuityWith, ancient Assyrians]
-
A.
historicalContinuity
chosen
Indicates that a relationship, pattern, or state persists over time in a way that links past conditions or events to present ones without significant interruption or change.
-
B.
historicallyExtendedBy
Indicates that something has been continued, expanded, or carried forward over time by another, later entity or development.
-
C.
hasHistoricalContext
Indicates that something is related to, influenced by, or best understood in light of specific past events, conditions, or time periods.
-
D.
historicallyBorneBy
Indicates that an entity has carried, possessed, or used another entity (such as a name, title, or symbol) at some point in the past.
-
E.
historicalReference
Indicates that one entity refers to, cites, or alludes to another entity from an earlier time or historical context.
- 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_69a2e7f55c60819097aff65ea2ca2832 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec5bdc848190826701590070497b |
completed | Feb. 28, 2026, 1:23 p.m. |
| PD | Predicate disambiguation | batch_69a2e96960608190bdd342da9c5ddb5e |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.