Triple
T17732768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hermopolitan Ogdoad |
E442627
|
entity |
| Predicate | conceptualAspect |
P128794
|
FINISHED |
| Object | primordial waters |
—
|
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: primordial waters | Statement: [Hermopolitan Ogdoad, conceptualAspect, primordial waters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conceptualAspect Context triple: [Hermopolitan Ogdoad, conceptualAspect, primordial waters]
-
A.
conceptualType
Indicates that one entity represents the conceptual category, class, or abstract type to which another entity belongs.
-
B.
conceptualScope
Indicates the range or domain of ideas, concepts, or topics that something (such as a work, theory, or term) is intended to cover or address.
-
C.
isConceptual
Indicates that something exists as an abstract or theoretical idea rather than as a concrete, physical entity.
-
D.
ontologicalAspect
Indicates a fundamental mode or category of being that characterizes how something exists or is realized.
-
E.
conceptualizedFor
Indicates that one entity has been conceived, designed, or mentally framed specifically for use, application, or relevance to another entity.
- F. None of above. chosen
Provenance (4 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_69d8b9ec79688190b86bdcef85a7b3aa |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e478e86f188190a5dd7fb32fd04c7b |
completed | April 19, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69e3cde815e08190881972e2d80d151e |
completed | April 18, 2026, 6:31 p.m. |
| PDg | Predicate description generation | batch_69e3d37ab6988190bd326ea6f8dd4aaa |
completed | April 18, 2026, 6:54 p.m. |
Created at: April 10, 2026, 10:08 a.m.