Triple
T4852335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joab |
E108444
|
entity |
| Predicate | religiousSiteAssociated |
P916
|
FINISHED |
| Object | altar in the tabernacle |
—
|
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: altar in the tabernacle | Statement: [Joab, religiousSiteAssociated, altar in the tabernacle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousSiteAssociated Context triple: [Joab, religiousSiteAssociated, altar in the tabernacle]
-
A.
religiousSiteType
Indicates the specific kind or category of religious site associated with an entity (e.g., church, mosque, temple).
-
B.
hasReligiousSite
chosen
Indicates that a location or entity possesses, contains, or is associated with a religious site such as a temple, church, mosque, shrine, or similar place of worship.
-
C.
religiousSiteAffected
Indicates that a religious site is impacted or influenced by a particular event, action, or condition.
-
D.
religiousSiteRank
Indicates the hierarchical or status-based rank assigned to a religious site within a religious or organizational structure.
-
E.
associatedTemple
Indicates a relationship where one entity is linked or connected to a particular temple, typically as its relevant or related religious site.
- 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_69bd440a89548190a5f14ba6da6b97dc |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ddd17d881909f7731ff2b460e83 |
completed | March 20, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69bd6c2557388190a2d15571bacd24f3 |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:26 p.m.