Triple
T28119049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Julii Mento |
E710723
|
entity |
| Predicate | hasTypeOfNameElement |
P59070
|
FINISHED |
| Object | cognomen-based branch name |
—
|
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: cognomen-based branch name | Statement: [Julii Mento, hasTypeOfNameElement, cognomen-based branch name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfNameElement Context triple: [Julii Mento, hasTypeOfNameElement, cognomen-based branch name]
-
A.
hasNameElementType
chosen
Indicates that something includes a specific type or category of element within its name.
-
B.
hasTypeOfNames
Indicates that one entity possesses or is associated with a particular category or kind of names defined by another entity.
-
C.
hasElementName
Indicates that an entity is associated with, or identified by, a specific element name.
-
D.
hasTypeName
Indicates that an entity is associated with a specific type name used to classify or identify its kind.
-
E.
hasElementType
Indicates that something is composed of or contains elements that are of a specified type.
- 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_69ef9b72f63081909dfbc2c1ddae86c6 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
Created at: April 27, 2026, 9:16 p.m.