Triple
T20927880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Julian family |
E515391
|
entity |
| Predicate | originLegendSource |
P141719
|
FINISHED |
| Object | Roman tradition |
—
|
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: Roman tradition | Statement: [Julian family, originLegendSource, Roman tradition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originLegendSource Context triple: [Julian family, originLegendSource, Roman tradition]
-
A.
regionOfLegend
Indicates the geographic area or locale with which a particular legend or myth is associated.
-
B.
inLegendRole
Indicates that an entity appears in a legendary or mythic context fulfilling a specific narrative or symbolic role.
-
C.
mentionsLegend
Indicates that one entity makes reference to or cites a legendary figure, story, or concept associated with another entity.
-
D.
authorOfPrimaryLegend
Indicates that one entity is the main creator or writer responsible for the primary legend associated with another entity.
-
E.
legend
Indicates that an entity is a traditional or historical story, figure, or narrative widely regarded as legendary rather than strictly factual.
- F. None of above. chosen
Provenance (4 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_69e0b4fb431c8190b9d40e6a72f0cc87 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6f652c3188190ace50415b3b30b83 |
completed | April 21, 2026, 4 a.m. |
| PD | Predicate disambiguation | batch_69e5c9af1fe08190953366a466950140 |
completed | April 20, 2026, 6:37 a.m. |
| PDg | Predicate description generation | batch_69e5d53d22d08190bc17ed4bed53804a |
completed | April 20, 2026, 7:26 a.m. |
Created at: April 16, 2026, 12:49 p.m.