Triple
T5364010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scylla |
E103086
|
entity |
| Predicate | hasVariantTraditions |
P46023
|
FINISHED |
| Object | parentage |
—
|
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: parentage | Statement: [Scylla, hasVariantTraditions, parentage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVariantTraditions Context triple: [Scylla, hasVariantTraditions, parentage]
-
A.
variantTraditions
chosen
Indicates that there exist differing or alternative traditions or customary practices associated with the same subject or context.
-
B.
hasAlternativeParentTraditions
Indicates that an entity is associated with additional, non-primary parent traditions beyond its main lineage or origin.
-
C.
hasChildInSomeTraditions
Indicates that, in at least some cultural, religious, or historical traditions, one entity is regarded as the child or offspring of another.
-
D.
hasSourceTradition
Indicates that something originates from, or is derived within, a particular cultural, religious, intellectual, or historical tradition.
-
E.
hasVariantReadingsWith
Indicates a relationship where two textual items are linked because they exhibit differing or alternative readings of (typically) the same underlying content.
- 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_69bd43daa3e4819090b59d127db70e57 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd865d42508190a1a96121674c1020 |
completed | March 20, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69bd845f41f88190b75b8b64b9e41862 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:02 p.m.