Triple
T9449361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miles Coverdale |
E227846
|
entity |
| Predicate | perspectiveOnCommunity |
P34688
|
FINISHED |
| Object | skeptical participant |
—
|
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: skeptical participant | Statement: [Miles Coverdale, perspectiveOnCommunity, skeptical participant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: perspectiveOnCommunity Context triple: [Miles Coverdale, perspectiveOnCommunity, skeptical participant]
-
A.
focusesOnCommunity
Indicates that the subject prioritizes and directs attention or effort toward the well-being, needs, or development of a community.
-
B.
viewOnCommunity
chosen
Indicates a perspective, opinion, or stance that an entity holds regarding a particular community.
-
C.
communityAspect
Indicates that something pertains to, reflects, or influences the communal or social dimension of a group or community.
-
D.
roleInCommunity
Indicates the function, position, or set of responsibilities an entity holds within a particular community or group.
-
E.
influencesCommunity
Indicates that one entity has an effect on the behavior, attitudes, or conditions of a community.
- 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_69ca8439f8bc8190997f2ef40c9f0bc2 |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd7f64fdc88190aec27793bfe62d77 |
completed | April 1, 2026, 8:26 p.m. |
| PD | Predicate disambiguation | batch_69cca5596ffc819097e9c8eefd4ef9b8 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:51 p.m.