Triple
T3142311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Issachar |
E65677
|
entity |
| Predicate | tribeReputation |
P45624
|
FINISHED |
| Object | men who understood the times |
—
|
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: men who understood the times | Statement: [Issachar, tribeReputation, men who understood the times]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tribeReputation Context triple: [Issachar, tribeReputation, men who understood the times]
-
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.
loyaltyProgramEarnings
Indicates the amount or details of rewards or benefits a participant accrues within a loyalty or rewards program.
-
C.
sharesTribeWith
Indicates that two entities belong to the same tribe or tribal group.
-
D.
tacticalReputation
Indicates the perceived level of skill, reliability, or effectiveness an entity has in planning and executing tactics within a given context.
-
E.
performanceReputation
Indicates the perceived quality or reliability of an entity’s past or expected performance as judged by others.
- 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_69ad8582f564819088c27e1f96153938 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada579b07c8190a7b316f499911a2d |
completed | March 8, 2026, 4:36 p.m. |
| PD | Predicate disambiguation | batch_69ad9df840088190a26a1516f4c1f056 |
completed | March 8, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69ada0f7c21c819087e9992f5fe30a37 |
completed | March 8, 2026, 4:16 p.m. |
Created at: March 8, 2026, 3:05 p.m.