Triple
T35569419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sulpicia |
E1027868
|
entity |
| Predicate | attestedPeriod |
P123510
|
FINISHED |
| Object | late Roman Republic |
—
|
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: late Roman Republic | Statement: [Sulpicia, attestedPeriod, late Roman Republic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attestedPeriod Context triple: [Sulpicia, attestedPeriod, late Roman Republic]
-
A.
establishedPeriod
Indicates the time span or date range during which something was founded, created, or formally brought into existence.
-
B.
refersToPeriod
Indicates that one entity designates, references, or is associated with a specific time period or interval.
-
C.
appliedDuringPeriod
Indicates that an action, condition, or status was in effect throughout a specified time period.
-
D.
timePeriodAttributed
chosen
Indicates that a specific time period is assigned or associated with an entity as its relevant temporal context.
-
E.
appearsInTimePeriod
Indicates that an entity is present, active, or occurs within a specified time period.
- 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_69f76e020fd8819081cb080e7e203083 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79ec355048190af30123ceb6efa2b |
completed | May 3, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69f79e4bdbcc8190be7a0d2cf8a77b64 |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:04 p.m.