Triple
T28410644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Augusta |
E719652
|
entity |
| Predicate | firstKnownUseContext |
P144603
|
FINISHED |
| Object | early Roman Empire |
—
|
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: early Roman Empire | Statement: [Augusta, firstKnownUseContext, early Roman Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstKnownUseContext Context triple: [Augusta, firstKnownUseContext, early Roman Empire]
-
A.
firstHistoricalUse
Indicates that the subject entity represents the earliest known or recorded instance of the object entity being used or occurring in history.
-
B.
firstUsedFor
Indicates that one entity was the earliest or original thing for which another entity was used or applied.
-
C.
firstUsedAs
Indicates that one entity was the earliest or original thing in which another entity was used or applied.
-
D.
isIntroducedInContextOf
chosen
Indicates that one entity is presented, mentioned, or brought into consideration specifically within the scope, situation, or circumstances defined by another entity.
-
E.
firstProminentUse
Indicates the earliest notable or widely recognized instance in which something was used in a significant or influential way.
- 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_69eff6f0f37c8190b37bc6fab08a9449 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_6a000fda03948190881b7275f249768f |
completed | May 10, 2026, 4:55 a.m. |
| PD | Predicate disambiguation | batch_6a000f607f1881908ee750d58da91690 |
completed | May 10, 2026, 4:53 a.m. |
Created at: April 28, 2026, 1:26 a.m.