Triple
T23573624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regium Julium |
E580185
|
entity |
| Predicate | ancientEthnicName |
P118880
|
FINISHED |
| Object | Regini |
—
|
NE NERFINISHED |
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: Regini | Statement: [Regium Julium, ancientEthnicName, Regini]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ancientEthnicName Context triple: [Regium Julium, ancientEthnicName, Regini]
-
A.
hasAncientEthnicName
chosen
Indicates that an entity is associated with an ethnic name or designation that originates from ancient times.
-
B.
ancientNameOf
Indicates that one entity is the historical or ancient name by which the other entity was formerly known.
-
C.
ethnonymAttestedIn
Indicates that the name of an ethnic group (ethnonym) is documented or recorded in a specified source, context, or medium.
-
D.
ethnonymRoot
Indicates that one term serves as the morphological or etymological root from which an ethnonym (a name for an ethnic group or people) is derived.
-
E.
hasNameEtymologyIn
Indicates that the origin or derivation of an entity’s name is based in, or traceable to, a specified source such as a language, place, or cultural 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_69e24601a9108190bc31e83833c980e4 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1afd4cde48190b5e4eb162d772319 |
completed | April 29, 2026, 7:14 a.m. |
| PD | Predicate disambiguation | batch_69f118bcc0b08190b25a8dddfd461a0e |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:37 p.m.