Triple
T11199607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hera Lacinia |
E265003
|
entity |
| Predicate | cultContinuityInto |
P72327
|
FINISHED |
| Object | Roman era |
—
|
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 era | Statement: [Hera Lacinia, cultContinuityInto, Roman era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cultContinuityInto Context triple: [Hera Lacinia, cultContinuityInto, Roman era]
-
A.
cultContinuity
chosen
Indicates the continuation or persistence of a religious cult’s practices, beliefs, or traditions over time.
-
B.
laterIdentityContinuityWith
Indicates that an entity at a later time is considered the same continuing individual or identity as an entity at an earlier time.
-
C.
continuedBy
Indicates that one entity carries on, extends, or resumes the activity, process, or sequence initiated by another entity.
-
D.
belongsToContinuity
Indicates that something is part of, or exists within, a specific narrative or temporal continuity.
-
E.
franchiseContinuity
Indicates that two works belong to the same narrative franchise or continuity, sharing a consistent storyline, universe, or canon.
- 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_69d6aa9eb9248190b20211772621b4bc |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8c1e9f88190b2b42326aba9d778 |
completed | April 9, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69d75cf83464819087529d47d025d313 |
completed | April 9, 2026, 8:02 a.m. |
Created at: April 8, 2026, 9:29 p.m.