Triple
T36565708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mamercinus |
E901969
|
entity |
| Predicate | relatedPraenomen |
P70695
|
FINISHED |
| Object | Mamercus |
E900023
|
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: Mamercus | Statement: [Mamercinus, relatedPraenomen, Mamercus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedPraenomen Context triple: [Mamercinus, relatedPraenomen, Mamercus]
-
A.
praenomenLinkedDeity
Indicates that a person's praenomen (given name) is etymologically or culturally linked to, derived from, or associated with a particular deity.
-
B.
isPraenomenOf
chosen
Indicates that a given personal name functions as the praenomen (given name) of a specific individual.
-
C.
praenomenOrNomen
Indicates that the related name element functions either as a personal given name (praenomen) or as a family/clan name (nomen) within a naming system.
-
D.
praenomenCommonlyUsed
Indicates that a particular praenomen (personal first name) is commonly used or frequently occurring within a given context or population.
-
E.
royalPrenomen
Indicates the formal throne name adopted by a monarch as part of their royal titulary.
- F. None of above.
Provenance (4 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_69f76e6416708190a9754b8c52d4e453 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3d178366808190b0363a997318a30d |
completed | June 25, 2026, 11:56 a.m. |
| PD | Predicate disambiguation | batch_6a037a0bf4b88190bdcfae9a14b51f0a |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:11 p.m.