Triple
T7252877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Most Holy Place |
E157645
|
entity |
| Predicate | genderOfPriestAccess |
P39348
|
FINISHED |
| Object | male |
—
|
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: male | Statement: [Most Holy Place, genderOfPriestAccess, male]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: genderOfPriestAccess Context triple: [Most Holy Place, genderOfPriestAccess, male]
-
A.
genderRule
Indicates a rule or constraint that determines how gender-related properties or classifications should be assigned or interpreted in a given context.
-
B.
hasGenderOfPerson
chosen
Indicates that a person is associated with a specific gender classification.
-
C.
hasGenderInterpretation
Indicates that an entity is associated with a particular interpretation or understanding of gender.
-
D.
genderPracticeVariesBy
Indicates that the way gender is expressed, understood, or practiced differs depending on the specific context, group, or setting involved.
-
E.
hasGenderRole
Indicates that an entity is associated with, or expected to perform, a particular socially defined gender-based role or set of behaviors.
- 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_69c6882d81d4819085f7ff862951ee4f |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6ea9d41908190bb76c6a5b9d5b1a2 |
completed | March 27, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69c6e7666ffc81908bf643d8257e6337 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:56 p.m.