Triple
T31048630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bojano |
E791194
|
entity |
| Predicate | hasAncientStatus |
P28623
|
FINISHED |
| Object | Roman municipium |
—
|
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: Roman municipium | Statement: [Bojano, hasAncientStatus, Roman municipium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAncientStatus Context triple: [Bojano, hasAncientStatus, Roman municipium]
-
A.
isAncient
Indicates that the entity existed or originated in a very distant past, typically far earlier than the commonly referenced historical period.
-
B.
hasAncientMember
Indicates that at least one member of a group, set, or collection originates from or belongs to an ancient time period.
-
C.
usedInAncientState
Indicates that something was utilized or practiced within the context of an ancient state or civilization.
-
D.
oldestStatus
Indicates that the associated status is the earliest or longest-standing one in a sequence of statuses for an entity.
-
E.
historicalStatusOf
chosen
Indicates the historical condition, role, or classification that an entity held during a specific past period or 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_69f224ca2fa881908a3ac5fedf207b90 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f78c61ed4c8190ad84c918fa9af55a |
completed | May 3, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69f78b8cb3a881909ebaac1b503988c2 |
completed | May 3, 2026, 5:53 p.m. |
Created at: April 29, 2026, 9 p.m.