Triple
T26643616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kings Park community |
E668845
|
entity |
| Predicate | receivesSupportType |
P936
|
FINISHED |
| Object | religious services |
—
|
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: religious services | Statement: [Kings Park community, receivesSupportType, religious services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: receivesSupportType Context triple: [Kings Park community, receivesSupportType, religious services]
-
A.
typeOfSupport
chosen
Indicates the kind or category of assistance, help, or backing provided in a given context.
-
B.
supportsType
Indicates that one entity is capable of handling, accepting, or being compatible with a specified type.
-
C.
providesSupportTo
Indicates that one entity offers help, resources, or reinforcement to another entity to aid its function, stability, or success.
-
D.
hasTypeOfSupport
Indicates that one entity provides or is associated with a particular kind or category of support in relation to another entity.
-
E.
supportedIn
Indicates that one entity is valid, applicable, or functionally enabled within the context, environment, platform, or scope defined by another entity.
- 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_69ee9d00eb5481908d6c6d0ada2f0c9a |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641dc8ff48190ab575d855616580c |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 2:30 a.m.