Triple
T17672476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maeonia |
E440556
|
entity |
| Predicate | knownFromSourceType |
P4092
|
FINISHED |
| Object | mythological traditions |
—
|
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: mythological traditions | Statement: [Maeonia, knownFromSourceType, mythological traditions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: knownFromSourceType Context triple: [Maeonia, knownFromSourceType, mythological traditions]
-
A.
knownFrom
chosen
Indicates that one entity is aware of, has learned about, or recognizes another entity through a specified source, context, or medium.
-
B.
usesSourceType
Indicates that one entity makes use of, relies on, or operates based on a particular type or category of source.
-
C.
isBestKnownFrom
Indicates that an entity is primarily or most famously recognized in connection with a particular source, context, or work.
-
D.
containsSourceOf
Indicates that one entity includes, holds, or encompasses the origin or cause of another entity.
-
E.
mainSourceType
Indicates the primary category or kind of source from which something originates or is derived.
- 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_69d8b9e87e18819087104a44dc4dc5b1 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e46f69b11c8190b09add33f81776b3 |
completed | April 19, 2026, 6 a.m. |
| PD | Predicate disambiguation | batch_69e3cde007d8819090dd92eea9f022cc |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 10 a.m.