Triple
T28773780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isaurian tribes |
E726478
|
entity |
| Predicate | producedNotableMember |
P129657
|
FINISHED |
| Object | Emperor Zeno |
—
|
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: Emperor Zeno | Statement: [Isaurian tribes, producedNotableMember, Emperor Zeno]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: producedNotableMember Context triple: [Isaurian tribes, producedNotableMember, Emperor Zeno]
-
A.
notableProducer
Indicates that an entity is a significant or well-known producer associated with another entity, such as a work, product, or project.
-
B.
producedNotableFiguresIn
chosen
Indicates that one entity (such as a place or institution) has given rise to or been the origin of notable or distinguished individuals associated with it.
-
C.
notableFamilyProduced
Indicates that a notable family is responsible for producing, creating, or giving rise to a particular person, group, or entity.
-
D.
notableProductionFor
Indicates that an entity is especially well-known or recognized for producing or creating another specified entity.
-
E.
producedMember
Indicates that one entity created, manufactured, or generated another entity as its product or output.
- 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_69f03199997c8190b6ae43fb19312443 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
Created at: April 28, 2026, 6:17 a.m.