Triple
T29063283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Veliternus |
E735597
|
entity |
| Predicate | modernEquivalentExpression |
P21626
|
FINISHED |
| Object | person from Velletri |
—
|
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: person from Velletri | Statement: [Veliternus, modernEquivalentExpression, person from Velletri]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernEquivalentExpression Context triple: [Veliternus, modernEquivalentExpression, person from Velletri]
-
A.
modernEquivalent
chosen
Indicates that one entity serves as the contemporary or updated counterpart of another earlier or traditional entity.
-
B.
equivalentEnglishForm
Indicates that two expressions share the same meaning in English, serving as equivalent linguistic forms.
-
C.
equivalentIn
Indicates that two entities are considered logically or functionally the same in meaning, status, or effect within a given context.
-
D.
hasModernExpression
Indicates that something possesses a contemporary or up-to-date form, style, or representation.
-
E.
equivalentTo
Indicates that two entities represent the same concept, value, or state, and can be treated as interchangeable in the given 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_69f077e85498819088b65186550da8cd |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f73ae120bc8190bff94d38d7a7a00d |
completed | May 3, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69f73a38d0848190aa5139144b8561c6 |
completed | May 3, 2026, 12:06 p.m. |
Created at: April 28, 2026, 10:16 a.m.