Triple
T6466958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ring of Solomon |
E142254
|
entity |
| Predicate | hasFunctionInLegends |
P70964
|
FINISHED |
| Object | sign of divine favor |
—
|
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: sign of divine favor | Statement: [Ring of Solomon, hasFunctionInLegends, sign of divine favor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFunctionInLegends Context triple: [Ring of Solomon, hasFunctionInLegends, sign of divine favor]
-
A.
hasFunctionInPresent
Indicates that an entity currently performs, exhibits, or fulfills a specific function or role at the present time.
-
B.
containsFunction
Indicates that one entity includes, defines, or provides the implementation of a particular function.
-
C.
hasFunctionInComplex
Indicates that an entity performs a specific functional role within a larger molecular or structural complex.
-
D.
hasFunctionInPlot
Indicates that an entity serves a particular role or purpose within the structure or progression of a plot.
-
E.
hasNameFunction
Indicates that an entity is associated with a function whose purpose is to provide or determine its name.
- 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_69c008d3bf4c8190bcf798c5ba9d6fb3 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06a12ccf481908f71f888cd744b64 |
completed | March 22, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69c0673d46a08190bc8bcd29f9555fe7 |
completed | March 22, 2026, 10:03 p.m. |
| PDg | Predicate description generation | batch_69c067da970481908a038995ba7dfb4b |
completed | March 22, 2026, 10:06 p.m. |
Created at: March 22, 2026, 4:49 p.m.