Triple
T8926332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman Venus (partially) |
E212546
|
entity |
| Predicate | sharesFunctionsWith |
P5696
|
FINISHED |
| Object | Inanna as goddess of love |
—
|
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: Inanna as goddess of love | Statement: [Roman Venus (partially), sharesFunctionsWith, Inanna as goddess of love]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesFunctionsWith Context triple: [Roman Venus (partially), sharesFunctionsWith, Inanna as goddess of love]
-
A.
sharesUniverseWith
Indicates that two entities exist within the same fictional or narrative universe, implying shared continuity, setting, or canon.
-
B.
sharesFeatureWith
chosen
Indicates that two entities have at least one common attribute, property, or characteristic in common.
-
C.
sharesModuleWith
Indicates that two entities are associated with or participate in at least one common module.
-
D.
sharesElementsWith
Indicates that two entities have one or more elements or components in common.
-
E.
sharesBaseWith
Indicates that two entities have a common underlying base element, source, or component from which they are derived or constructed.
- 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_69ca839481d48190b42b037e0d0f636c |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc66700fb48190874563e535f20437 |
completed | April 1, 2026, 12:27 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed3286c8190a21de2ee11f2639f |
completed | March 31, 2026, 11:54 p.m. |
Created at: March 30, 2026, 6:57 p.m.