Triple
T35848680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maacah |
E1036285
|
entity |
| Predicate | positionRelativeToCourt |
P22449
|
FINISHED |
| Object | member of royal court of Judah |
—
|
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: member of royal court of Judah | Statement: [Maacah, positionRelativeToCourt, member of royal court of Judah]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionRelativeToCourt Context triple: [Maacah, positionRelativeToCourt, member of royal court of Judah]
-
A.
positionInCourt
chosen
Indicates the specific role or standing an entity holds within a court setting or judicial proceeding.
-
B.
positionInCourtHierarchy
Indicates the relative rank or level that one court holds within a judicial or court system’s hierarchy.
-
C.
positionInTennis
Indicates the specific role or court location a player occupies during a tennis match or point.
-
D.
primaryLocationOnCourt
Indicates the main area or position on the court where an entity is typically located or operates.
-
E.
relativePositionInStadium
Indicates the spatial relationship between entities based on where they are located relative to each other within a stadium.
- 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_69f76e1a29e8819088280f26096aeb55 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff8cecbf048190860b9f72b8753f5c |
completed | May 9, 2026, 7:37 p.m. |
| PD | Predicate disambiguation | batch_69ff8c4c39dc8190b5bf35adc1bae7c6 |
completed | May 9, 2026, 7:34 p.m. |
Created at: May 3, 2026, 4:06 p.m.