Triple
T2024528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pittsburgh Platform |
E44177
|
entity |
| Predicate | viewOfMoralLaw |
P19251
|
FINISHED |
| Object | permanently binding |
—
|
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: permanently binding | Statement: [Pittsburgh Platform, viewOfMoralLaw, permanently binding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: viewOfMoralLaw Context triple: [Pittsburgh Platform, viewOfMoralLaw, permanently binding]
-
A.
viewOnMoralLaw
chosen
Indicates a subject’s stance or interpretation regarding principles of moral law or ethical rules.
-
B.
viewOfGod
Indicates a relationship where an entity holds a particular conception, perspective, or understanding of God.
-
C.
hasMoralPerspective
Indicates that an entity holds or applies a particular moral or ethical viewpoint in evaluating actions, situations, or other entities.
-
D.
viewsAsVirtue
Indicates that one entity regards a particular trait, behavior, or quality as a moral virtue.
-
E.
viewOnGod
Indicates a relationship where one entity holds or expresses a particular opinion, belief, or perspective about God.
- 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_69a8891201bc8190aca837be6de41579 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb8f2cd5c8190b19da6f6aa2001d6 |
completed | March 7, 2026, 5:34 a.m. |
| PD | Predicate disambiguation | batch_69abb7a656248190ac2ced196b35bc6b |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:38 p.m.