Triple
T8924897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gnaeus Pompeius Magnus |
E212515
|
entity |
| Predicate | praenomen |
P7966
|
FINISHED |
| Object | Gnaeus |
E222442
|
NE 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: Gnaeus | Statement: [Gnaeus Pompeius Magnus, praenomen, Gnaeus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gnaeus Context triple: [Gnaeus Pompeius Magnus, praenomen, Gnaeus]
-
A.
Gnaeus
chosen
Gnaeus is the praenomen (given name) of the prominent Roman general and statesman Pompey the Great.
-
B.
Gaius
Gaius was a prominent 2nd-century Roman jurist whose legal writings, especially his Institutes, significantly shaped later Roman and European legal traditions.
-
C.
Gaius
Gaius is an early Christian believer and church member addressed personally and commended by the Apostle John in the New Testament.
-
D.
Gaius
Gaius is the praenomen (personal name) of the Roman lawyer, author, and magistrate known as Pliny the Younger.
-
E.
Gaius
Gaius is a common Roman praenomen (given name) frequently borne by notable figures of the Roman Republic and Empire.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca839481d48190b42b037e0d0f636c |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc66547de881909ea9bfd104b32893 |
completed | April 1, 2026, 12:27 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d1c3f31db48190a63d0d60f108496f |
completed | April 5, 2026, 2:07 a.m. |
Created at: March 30, 2026, 6:57 p.m.