Triple
T14771790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Spirit |
E347151
|
entity |
| Predicate | descendsBy |
P115730
|
FINISHED |
| Object | God’s command |
—
|
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: God’s command | Statement: [The Spirit, descendsBy, God’s command]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: descendsBy Context triple: [The Spirit, descendsBy, God’s command]
-
A.
descentFrom
Indicates that one entity is a descendant of another, typically through a lineage or ancestral relationship.
-
B.
hasDescent
Indicates that one entity is a descendant of another, typically through a lineage or ancestry relationship.
-
C.
ofDescent
Indicates a genealogical or ancestral relationship, specifying that one entity descends from or originates from another.
-
D.
descentVia
Indicates a lineage relationship where one entity is descended from another through one or more intermediate generations or branches.
-
E.
descentSystem
Indicates the kinship or inheritance pattern through which lineage, membership, or rights are traced (e.g., matrilineal, patrilineal, or bilateral).
- 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_69d822e9b9e08190bedcc31a163fda82 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec81485e08190be35baafcf22b6f2 |
completed | April 14, 2026, 11:04 p.m. |
| PD | Predicate disambiguation | batch_69de8c02e5c08190943c27594026faf7 |
completed | April 14, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69de8f4b67cc8190b84b59fcec5cf579 |
completed | April 14, 2026, 7:02 p.m. |
Created at: April 10, 2026, 1:31 a.m.