Triple
T32821977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Forum Cornelii |
E839456
|
entity |
| Predicate | wasFoundedUnder |
P3647
|
FINISHED |
| Object | Roman authority |
—
|
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 authority | Statement: [Forum Cornelii, wasFoundedUnder, Roman authority]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasFoundedUnder Context triple: [Forum Cornelii, wasFoundedUnder, Roman authority]
-
A.
foundedUnder
chosen
Indicates that an entity was established or created during the tenure, authority, or jurisdiction of another entity (such as a leader, regime, or governing body).
-
B.
foundedAs
Indicates the original name or form under which an organization, institution, or entity was first established.
-
C.
foundedBefore
Indicates that one entity was established or created at an earlier time than the other entity.
-
D.
foundingOf
Indicates the event or relationship in which an entity is established or created, typically linking the founder(s), the founded entity, and the time or context of its creation.
-
E.
foundedOn
Indicates that an entity was established, created, or brought into existence on a specific date or point in time.
- 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_69f3493df9008190a8f5d843dcd77704 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6ce6d659881909ddcec1d2966e020 |
completed | May 3, 2026, 4:26 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1667a48190b42684f6ec22dae9 |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 1:15 a.m.