Triple
T25576858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sarah Sisko |
E641128
|
entity |
| Predicate | relationshipToProphets |
P29107
|
FINISHED |
| Object | temporary host |
—
|
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: temporary host | Statement: [Sarah Sisko, relationshipToProphets, temporary host]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToProphets Context triple: [Sarah Sisko, relationshipToProphets, temporary host]
-
A.
linkedToProphet
chosen
Indicates a relationship in which an entity is associated or connected in some meaningful way to a prophet.
-
B.
regardsLeaderAsProphet
Indicates that an individual views or treats their leader as a prophet, attributing prophetic authority or divine guidance to them.
-
C.
regardsAsOnlyProphetAfterMoses
Indicates that one entity considers another entity to be the sole legitimate prophet following Moses.
-
D.
relationshipToDeities
Indicates how an entity is connected or related to one or more deities, such as through worship, lineage, role, or status.
-
E.
linkedToPropheticBiography
Indicates a relationship where something is connected or related to a prophetic biography, such as the life, actions, or traditions of a prophet.
- 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_69e75dc281bc819095ec04dc0c3a94d0 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69fce7671f108190bf3ebf54339068b5 |
completed | May 7, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69fce5b5a84c81908ac1b5b9f08d48d0 |
completed | May 7, 2026, 7:19 p.m. |
Created at: April 21, 2026, 4:01 p.m.