Triple
T8924759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mucia Tertia |
E212512
|
entity |
| Predicate | mother |
P120
|
FINISHED |
| Object |
Licinia
Licinia was a Roman noblewoman of the late Republic, known primarily as the daughter of Mucia Tertia and thus connected to prominent political families of her time.
|
E766691
|
NE FINISHED |
How this triple was built (4 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: Licinia | Statement: [Mucia Tertia, mother, Licinia]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Licinia Context triple: [Mucia Tertia, mother, Licinia]
-
A.
Laibin
Laibin is a prefecture-level city in south-central China known for its role as a regional transportation hub and its mix of industrial and agricultural development.
-
B.
Lujza
Lujza is a given name, primarily used in Central and Eastern Europe, that corresponds to the name Luisa or Louise in other languages.
-
C.
Lubja
Lubja is a small village located within Viimsi Parish in northern Estonia, near the capital city of Tallinn.
-
D.
Lindinis
Lindinis is the Roman-era name for the town now known as Ilchester in Somerset, England, which served as an important settlement in Roman Britain.
-
E.
Lukin
Lukin is a component or module associated with the "No Code" system, likely serving as a distinct functional part within that broader platform.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Licinia Triple: [Mucia Tertia, mother, Licinia]
Generated description
Licinia was a Roman noblewoman of the late Republic, known primarily as the daughter of Mucia Tertia and thus connected to prominent political families of her time.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Licinia Target entity description: Licinia was a Roman noblewoman of the late Republic, known primarily as the daughter of Mucia Tertia and thus connected to prominent political families of her time.
-
A.
Laibin
Laibin is a prefecture-level city in south-central China known for its role as a regional transportation hub and its mix of industrial and agricultural development.
-
B.
Lujza
Lujza is a given name, primarily used in Central and Eastern Europe, that corresponds to the name Luisa or Louise in other languages.
-
C.
Lubja
Lubja is a small village located within Viimsi Parish in northern Estonia, near the capital city of Tallinn.
-
D.
Lindinis
Lindinis is the Roman-era name for the town now known as Ilchester in Somerset, England, which served as an important settlement in Roman Britain.
-
E.
Lukin
Lukin is a component or module associated with the "No Code" system, likely serving as a distinct functional part within that broader platform.
- F. None of above. chosen
Provenance (5 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_69cfba58e9ec81909141c516d05ac790 |
completed | April 3, 2026, 1:02 p.m. |
| NEDg | Description generation | batch_69cfbade9330819096d4b0eeacdad6da |
completed | April 3, 2026, 1:04 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69cfbec2b8888190a0390168fdcef05f |
completed | April 3, 2026, 1:21 p.m. |
Created at: March 30, 2026, 6:57 p.m.