Triple
T16477950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gibeonites |
E400235
|
entity |
| Predicate | culticFunction |
P59646
|
FINISHED |
| Object | servants for the house of God |
—
|
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: servants for the house of God | Statement: [Gibeonites, culticFunction, servants for the house of God]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: culticFunction Context triple: [Gibeonites, culticFunction, servants for the house of God]
-
A.
cultFunction
chosen
Indicates that one entity serves as a religious or ritual function, role, or purpose in relation to another entity within a cultic or worship context.
-
B.
functionInRitual
Indicates that an entity serves a specific role or performs a particular function within a ritual.
-
C.
covens
Indicates that one or more entities secretly cooperate or conspire together, often for a shared hidden or illicit purpose.
-
D.
hasCulticPractice
Indicates that an entity engages in, observes, or is associated with a specific religious or ritualistic practice.
-
E.
typeOfCult
Indicates that one entity is a specific kind or category of cult relative to another entity.
- 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_69d883813098819084f5409539723b59 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e0013ac8190b607d5f47d17c501 |
completed | April 18, 2026, 7:08 a.m. |
| PD | Predicate disambiguation | batch_69e22706b0588190a48a951c5211a617 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:13 a.m.