Triple
T2673467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | George Ripley |
E56402
|
entity |
| Predicate | socialReformFocus |
P41612
|
FINISHED |
| Object | communal living |
—
|
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: communal living | Statement: [George Ripley, socialReformFocus, communal living]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: socialReformFocus Context triple: [George Ripley, socialReformFocus, communal living]
-
A.
socialContribution
Indicates that an entity engages in actions or provides resources that benefit society or a community beyond its own direct interests.
-
B.
socialImpact
Indicates the extent to which an action, entity, or relationship affects society or communities, whether positively or negatively.
-
C.
socialStance
Indicates the attitude, position, or orientation one entity holds toward another in a social context.
-
D.
socialIssue
Indicates a relationship where something is recognized or treated as a problem or concern affecting society or a community at large.
-
E.
socialConcern
Indicates a relationship where an entity is concerned about, attentive to, or actively engaged with social issues, problems, or well-being.
- 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_69ab4a4b13fc81909dfdb3f23da46832 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd9b08b1c8190824342fc63e555d2 |
completed | March 7, 2026, 7:54 a.m. |
| PD | Predicate disambiguation | batch_69abd8190ad481908f3e14ac84d0940a |
completed | March 7, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69abd8f98c348190a68064c565589459 |
completed | March 7, 2026, 7:51 a.m. |
Created at: March 6, 2026, 9:54 p.m.