Triple
T18693880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Personifications in Greek mythology |
E457065
|
entity |
| Predicate | haveForm |
P169
|
FINISHED |
| Object | anthropomorphic deities |
—
|
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: anthropomorphic deities | Statement: [Personifications in Greek mythology, haveForm, anthropomorphic deities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: haveForm Context triple: [Personifications in Greek mythology, haveForm, anthropomorphic deities]
-
A.
hasForm
chosen
Indicates that one entity possesses, exhibits, or is characterized by a particular shape, structure, or configuration.
-
B.
hasFormFor
Indicates that one entity possesses or provides a specific form or document intended to be used by another entity or for a particular purpose.
-
C.
hasFormed
Indicates that an entity has come together or been created into a particular structure, group, or configuration.
-
D.
containsForm
Indicates that one entity includes or encapsulates another entity as a form, structure, or representation within it.
-
E.
hasOnlineForm
Indicates that an entity provides or is associated with a form that can be accessed and completed online.
- 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_69d8d391eb488190ac2e9abf5bf255e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e562e581f48190997d279296a31e7f |
completed | April 19, 2026, 11:19 p.m. |
| PD | Predicate disambiguation | batch_69e478de85088190ba5f005f1d39f587 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:49 a.m.