Triple
T9401450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aesernia |
E226480
|
entity |
| Predicate | importanceToSamnites |
P88741
|
FINISHED |
| Object | major urban center |
—
|
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: major urban center | Statement: [Aesernia, importanceToSamnites, major urban center]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: importanceToSamnites Context triple: [Aesernia, importanceToSamnites, major urban center]
-
A.
importanceToAllies
Indicates the degree to which an entity is considered valuable, influential, or strategically significant to its allies.
-
B.
aimOfRome
Indicates that something is the goal, purpose, or intended objective of Rome.
-
C.
importantSaint
Indicates that the subject is recognized as a particularly significant or highly revered saint within a religious or spiritual tradition.
-
D.
militaryImportance
Indicates the degree to which something is strategically or operationally significant to military objectives or capabilities.
-
E.
peakImportance
Indicates that something reaches or represents the highest level of importance within a given context or timeframe.
- 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_69ca843170f88190800a8ab2b5fc568e |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd5157d66c819094c18f680c7093f7 |
completed | April 1, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69cca545b2448190a4297312e39c21ac |
completed | April 1, 2026, 4:55 a.m. |
| PDg | Predicate description generation | batch_69cca89b3368819087a3d69270c1f185 |
completed | April 1, 2026, 5:09 a.m. |
Created at: March 30, 2026, 7:46 p.m.