Triple
T37287545
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pseudo-Phalaris letters tradition |
E925574
|
entity |
| Predicate | evaluatedFor |
P91138
|
FINISHED |
| Object | style |
—
|
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: style | Statement: [Pseudo-Phalaris letters tradition, evaluatedFor, style]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: evaluatedFor Context triple: [Pseudo-Phalaris letters tradition, evaluatedFor, style]
-
A.
evaluatesFor
Indicates that one entity assesses or judges something on behalf of, or for the benefit of, another entity.
-
B.
evaluatedInContext
chosen
Indicates that an entity (such as a statement, result, or behavior) is assessed or interpreted within a specific contextual setting or framework.
-
C.
evaluatesAs
Indicates that one entity is judged, interpreted, or assessed as having a particular value, role, or classification in relation to another.
-
D.
hasEvaluation
Indicates that an entity has been assessed or judged according to some criteria, linking it to the corresponding evaluation result or record.
-
E.
executedFor
Indicates that one entity carried out an action, task, or operation on behalf of or in fulfillment of an obligation to another entity.
- 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_69f76eafe20c8190856d3b996a4c31a7 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb78cbef988190b8f79d946b46e6b2 |
completed | May 6, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9ac5a08190b24ef308963fc52b |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:16 p.m.