Triple
T7175460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Byzas of Megara |
E167307
|
entity |
| Predicate | saidToBeTheOriginOf |
P1823
|
FINISHED |
| Object | name of Byzantium |
—
|
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: name of Byzantium | Statement: [Byzas of Megara, saidToBeTheOriginOf, name of Byzantium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: saidToBeTheOriginOf Context triple: [Byzas of Megara, saidToBeTheOriginOf, name of Byzantium]
-
A.
depictsOriginOf
Indicates that one entity visually represents or illustrates the source, beginning, or point of origin of another entity.
-
B.
historicalOrigin
chosen
Indicates the relationship by which one entity serves as the source, origin, or starting point in history for another entity.
-
C.
originatesAs
Indicates that one entity begins, arises, or comes into existence in the form, state, or role specified by another entity.
-
D.
capitalOfOrigin
Indicates that one entity is the capital city associated with the origin (such as birthplace, founding place, or source location) of another entity.
-
E.
speciesOrigin
Indicates the place, environment, or source from which a species originally arose or evolved.
- 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_69c68889a2748190a316c5e65360361a |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e9b045c48190b27b2d6f7c11026f |
completed | March 27, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69c6e74fb0f48190b2ad4dd4efdd241a |
completed | March 27, 2026, 8:23 p.m. |
Created at: March 27, 2026, 2:48 p.m.