Triple
T21012957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hirom |
E517596
|
entity |
| Predicate | isUsedInContextOf |
P34621
|
FINISHED |
| Object | biblical names |
—
|
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: biblical names | Statement: [Hirom, isUsedInContextOf, biblical names]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUsedInContextOf Context triple: [Hirom, isUsedInContextOf, biblical names]
-
A.
isKnownInContextOf
Indicates that an entity is recognized, relevant, or has significance specifically within a given context or domain.
-
B.
isRaisedInContextOf
Indicates that an entity is brought up, discussed, or introduced within a particular situational, thematic, or conversational context.
-
C.
isReleasedInContextOf
Indicates that an entity is released or made available specifically within, or as part of, a particular context, situation, or framework.
-
D.
namedInContextOf
chosen
Indicates that an entity is mentioned or identified specifically within a particular context, situation, or frame of reference.
-
E.
appearsInContextWith
Indicates that two entities are observed or used together within the same situational, textual, or usage context.
- 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_69e0b50192308190a284fcc89dd23a49 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc41d57881908b9ab17d1844a8d0 |
completed | April 21, 2026, 4:25 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf274ac81909bbf245627dc8fdc |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:53 p.m.