Triple
T36944714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Curius |
E913872
|
entity |
| Predicate | romanNameComponent |
P82301
|
FINISHED |
| Object | nomen gentilicium |
—
|
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: nomen gentilicium | Statement: [Curius, romanNameComponent, nomen gentilicium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: romanNameComponent Context triple: [Curius, romanNameComponent, nomen gentilicium]
-
A.
romanNomen
Indicates that an entity has a specific Roman nomen, i.e., the clan or gens name within the traditional Roman naming system.
-
B.
romanCivitasName
Indicates that an entity bears the official Roman civitas (city or community) name associated with it.
-
C.
partOfRomanNamingSystem
chosen
Indicates that something functions as a component or element within the traditional Roman naming system.
-
D.
preRomanName
Indicates the name by which an entity (such as a place or people) was known before the Roman period or prior to receiving a Roman-era name.
-
E.
hasRomanName
Indicates that an entity is associated with or known by a name derived from or used in ancient Rome.
- 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_69f76e8a6a5c81909c1febf32bf3fe23 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fa0a7b00948190a257273d9968c5d7 |
completed | May 5, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69f9fec9c9488190ae2a349651a02782 |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:13 p.m.