Triple
T34650752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Πύρρος |
E889829
|
entity |
| Predicate | βασίλευσεΣε |
P10353
|
FINISHED |
| Object | Ήπειρος |
—
|
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: Ήπειρος | Statement: [Πύρρος, βασίλευσεΣε, Ήπειρος]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: βασίλευσεΣε Context triple: [Πύρρος, βασίλευσεΣε, Ήπειρος]
-
A.
suzerain
Indicates a relationship in which one entity holds overlordship or supreme authority over another, which remains internally autonomous but owes allegiance, tribute, or obedience.
-
B.
εκβάλλειΣτο
Indicates that one geographical feature (typically a river or stream) flows into and empties into another body of water.
-
C.
εξέδωσε
Indicates that an entity (typically a person or organization) has issued, published, or formally released something (such as a document, statement, or work).
-
D.
ruled in
Indicates that an authority, such as a court or judge, has made a formal decision or judgment in favor of a particular party or position.
-
E.
reignAs
chosen
Indicates that an entity holds and exercises ruling authority or sovereignty over a domain or people for a period of time.
- 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_69f349d825c88190bfc6170ac9281260 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f722c27e1c819098f67081bc0764b3 |
completed | May 3, 2026, 10:26 a.m. |
| PD | Predicate disambiguation | batch_69f72157af108190880317a62e634bb0 |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 2:04 a.m.