Triple
T34512463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parking |
E886059
|
entity |
| Predicate | hasMythologicalInfluence |
P126681
|
FINISHED |
| Object | Greek mythology |
—
|
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: Greek mythology | Statement: [Parking, hasMythologicalInfluence, Greek mythology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMythologicalInfluence Context triple: [Parking, hasMythologicalInfluence, Greek mythology]
-
A.
hasMythologicalBasis
chosen
Indicates that something is founded on, derived from, or significantly influenced by a mythological story, figure, or tradition.
-
B.
hasMythologicalUsage
Indicates that something is used, referenced, or functions within a mythological context or tradition.
-
C.
hasMythologicalFeature
Indicates that an entity possesses a characteristic, attribute, or element derived from mythology or mythological beings.
-
D.
hasMythologicalBelief
Indicates that an entity holds or subscribes to a particular mythological belief or set of mythological beliefs.
-
E.
hasMythologicalDomain
Indicates that a mythological figure, deity, or entity is associated with or rules over a particular conceptual or physical domain (such as the sea, war, or the underworld).
- 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_69f349ccc290819089d8e82698e53cb6 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7234bcaa48190ac970759d34e254a |
completed | May 3, 2026, 10:28 a.m. |
| PD | Predicate disambiguation | batch_69f72155c48881909bd40b9aa3febd5a |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 2:01 a.m.