Triple
T21617415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Franciscan theology |
E533480
|
entity |
| Predicate | viewsCreationAs |
P102849
|
FINISHED |
| Object | fundamentally good |
—
|
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: fundamentally good | Statement: [Franciscan theology, viewsCreationAs, fundamentally good]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: viewsCreationAs Context triple: [Franciscan theology, viewsCreationAs, fundamentally good]
-
A.
viewsAs
chosen
Indicates that one entity perceives, interprets, or regards another entity in a particular way or role.
-
B.
viewsClientAs
Indicates that one entity regards or treats another entity as a client within a service, business, or professional relationship.
-
C.
viewsAliAs
Indicates that one entity holds a particular perception, opinion, or characterization of Ali.
-
D.
viewsOtherPathsAs
Indicates that one entity perceives, interprets, or regards alternative paths, routes, or courses of action in a particular way relative to another entity.
-
E.
viewsBehaviorAs
Indicates that one entity interprets, judges, or regards another entity’s behavior in a particular way.
- 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_69e0c46411108190bba0d4176dffc9f3 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef3bab865081908bc7d7b1824415ac |
completed | April 27, 2026, 10:34 a.m. |
| PD | Predicate disambiguation | batch_69e69665fe8c8190af7e38785db188b2 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:34 p.m.