Triple
T36046204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pegasus |
E1042675
|
entity |
| Predicate | hasRomanEquivalentName |
P36249
|
FINISHED |
| Object | Pegasus |
—
|
NE NERFINISHED |
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: Pegasus | Statement: [Pegasus, hasRomanEquivalentName, Pegasus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRomanEquivalentName Context triple: [Pegasus, hasRomanEquivalentName, Pegasus]
-
A.
hasRomanEquivalent
chosen
Indicates that one entity corresponds to or is equivalent to another entity within the context of Roman culture, naming, or classification.
-
B.
hasRomanName
Indicates that an entity is associated with or known by a name derived from or used in ancient Rome.
-
C.
hasRomanNameStructure
Indicates that an entity’s name follows the conventional structural pattern of Roman naming (e.g., praenomen–nomen–cognomen or similar historically Roman forms).
-
D.
usesRomanNumerals
Indicates that something represents numbers or sequences using the Roman numeral system rather than standard Arabic digits.
-
E.
fullRomanName
Indicates that one entity is the complete Roman-style personal name (including all components) corresponding to another entity.
- 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_69f76e2e41f8819091f9fb0536920fec |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69feb342994081909481ec8ec5d44928 |
completed | May 9, 2026, 4:08 a.m. |
| PD | Predicate disambiguation | batch_69feb046e4e48190b96649aa28529cc9 |
completed | May 9, 2026, 3:55 a.m. |
Created at: May 3, 2026, 4:07 p.m.