Triple
T4309588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | גֵּיא בֶן־הִנֹּם |
E94037
|
entity |
| Predicate | laterReputation |
P56376
|
FINISHED |
| Object | unclean place |
—
|
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: unclean place | Statement: [גֵּיא בֶן־הִנֹּם, laterReputation, unclean place]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterReputation Context triple: [גֵּיא בֶן־הִנֹּם, laterReputation, unclean place]
-
A.
associatedWithReputation
Indicates a relationship where an entity is linked to, influenced by, or characterized in terms of another entity’s reputation or perceived standing.
-
B.
reputationBuiltFor
Indicates that one entity has established or developed a reputation specifically for or in relation to another entity.
-
C.
crowdReputation
Indicates the collective opinion or perceived standing of an entity as judged by a group or general audience.
-
D.
hasQuirkyReputation
Indicates that an entity is regarded by others as having an unusual, eccentric, or unconventional character or style.
-
E.
tacticalReputation
Indicates the perceived level of skill, reliability, or effectiveness an entity has in planning and executing tactics within a given context.
- F. None of above. chosen
Provenance (4 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_69b3451886588190a3dd1305ea7c58dc |
completed | March 12, 2026, 10:58 p.m. |
| NER | Named-entity recognition | batch_69b350d40748819084798058396be113 |
completed | March 12, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69b34f4a07b08190a06ada0d9cbb14fb |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b35034cd248190bae09e9d090e13ec |
completed | March 12, 2026, 11:45 p.m. |
Created at: March 12, 2026, 11:11 p.m.