Triple
T9371175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ninlil |
E225531
|
entity |
| Predicate | symbolicDomain |
P64550
|
FINISHED |
| Object | fertility |
—
|
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: fertility | Statement: [Ninlil, symbolicDomain, fertility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: symbolicDomain Context triple: [Ninlil, symbolicDomain, fertility]
-
A.
notationDomain
Indicates a relationship where a notation system is associated with, or defined over, a particular domain in which it is valid or applicable.
-
B.
domainOfVariables
Indicates that the predicate specifies the set or type of values that the variables involved in an expression or formula are allowed to take.
-
C.
symbolicAspect
chosen
Indicates that one entity functions as a symbol or emblem that represents, expresses, or conveys a particular meaning, quality, or concept of another entity.
-
D.
symbolicContinuity
Indicates that there is a consistent, ongoing use or preservation of the same symbols or symbolic forms across time, contexts, or instances.
-
E.
coordinateDomain
Indicates that two or more entities share the same coordinate system or spatial reference framework for describing positions.
- 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_69ca842cbddc819099d71ecec48cf9e5 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd5083cbb8819088e8cef26be1b380 |
completed | April 1, 2026, 5:06 p.m. |
| PD | Predicate disambiguation | batch_69cc7a6abb8c81908c7a2f4ee92cc949 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:43 p.m.