Triple
T9364673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Semo Sancus |
E225369
|
entity |
| Predicate | cultStatusInRome |
P88158
|
FINISHED |
| Object | early and archaic |
—
|
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 and archaic | Statement: [Semo Sancus, cultStatusInRome, early and archaic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cultStatusInRome Context triple: [Semo Sancus, cultStatusInRome, early and archaic]
-
A.
administrativeStatusUnderRome
Indicates the type or level of administrative control or governance an entity was subject to within the Roman political system.
-
B.
cultStatus
Indicates that something has achieved a devoted, niche following or admiration that is disproportionate to its mainstream popularity.
-
C.
romanStatus
Indicates the status or condition of an entity within a Roman-specific context, such as its legal, social, or civic standing in Roman society.
-
D.
laterRelationToRome
Indicates that one entity occurs or exists at a time later than the reference time associated with Rome.
-
E.
initialRelationToRome
Indicates the nature of an entity’s earliest recorded or original relationship, status, or connection to Rome.
- F. None of above. chosen
Provenance (4 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_69ca842bdd648190904131d58620d448 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd503fd7f081909655e2a880c84834 |
completed | April 1, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69cc7a6abb8c81908c7a2f4ee92cc949 |
completed | April 1, 2026, 1:52 a.m. |
| PDg | Predicate description generation | batch_69cc955a38108190b602d1e73725f11b |
completed | April 1, 2026, 3:47 a.m. |
Created at: March 30, 2026, 7:42 p.m.