Triple
T34621573
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heritage Grants |
E889016
|
entity |
| Predicate | typicalActivitiesFunded |
P1164
|
FINISHED |
| Object | conservation of historic buildings |
—
|
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: conservation of historic buildings | Statement: [Heritage Grants, typicalActivitiesFunded, conservation of historic buildings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalActivitiesFunded Context triple: [Heritage Grants, typicalActivitiesFunded, conservation of historic buildings]
-
A.
typicalActivity
chosen
Indicates that an entity is commonly or characteristically engaged in a particular activity.
-
B.
fundedEntityType
Indicates the type or category of entity that receives funding in the described funding relationship.
-
C.
fundedProject
Indicates that a funding entity has provided financial support to a specific project.
-
D.
activitiesCarriedOutFor
Indicates that certain activities are performed on behalf of, in service of, or for the benefit of a particular entity.
-
E.
encouragesActivities
Indicates that one entity promotes, supports, or motivates another entity to engage in certain activities.
- 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_69f349d64a388190a013cfa9bd33fad7 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fd7aac8190873077e63873aa72 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 2:04 a.m.