Triple
T5954851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | On Those Who Think They Are Justified by Works |
E132486
|
entity |
| Predicate | viewsWorksAs |
P67047
|
FINISHED |
| Object | expressions of faith |
—
|
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: expressions of faith | Statement: [On Those Who Think They Are Justified by Works, viewsWorksAs, expressions of faith]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: viewsWorksAs Context triple: [On Those Who Think They Are Justified by Works, viewsWorksAs, expressions of faith]
-
A.
worksAs
Indicates that an entity performs the role, job, or occupation specified by another entity.
-
B.
viewOver
Indicates that one entity has a visual perspective overlooking or facing another entity, typically providing a vantage point onto it.
-
C.
viewsArtAs
Indicates that one entity regards or interprets another entity as a form or example of art.
-
D.
worksTo
Indicates that one entity performs work or exerts effort in order to achieve, support, or contribute to another entity or outcome.
-
E.
viewsClientAs
Indicates that one entity regards or treats another entity as a client within a service, business, or professional relationship.
- 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_69c0086b05cc8190a8f36a96927a525c |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c03fb7f8a88190a8bd45208bda4a03 |
completed | March 22, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69c0335a635881909c58c1ef0f97f1e8 |
completed | March 22, 2026, 6:22 p.m. |
| PDg | Predicate description generation | batch_69c03fb6bb7c81909c5629fba408dc69 |
completed | March 22, 2026, 7:15 p.m. |
Created at: March 22, 2026, 4:02 p.m.