Triple
T4391272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trinity House |
E99366
|
entity |
| Predicate | hasCharitableFunction |
P56346
|
FINISHED |
| Object | support for seafarers |
—
|
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: support for seafarers | Statement: [Trinity House, hasCharitableFunction, support for seafarers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCharitableFunction Context triple: [Trinity House, hasCharitableFunction, support for seafarers]
-
A.
hasCharitableFoundation
Indicates that an entity maintains or is associated with a charitable foundation, typically for philanthropic or nonprofit activities.
-
B.
isPhilanthropic
Indicates that an entity habitually engages in generous actions or donations intended to promote the welfare of others.
-
C.
hasCharitySingle
Indicates that an entity is associated with exactly one specific charitable organization or charitable initiative.
-
D.
hasPhilanthropicRole
Indicates that an entity holds or performs a role related to charitable, philanthropic, or socially beneficial activities.
-
E.
associatedCharity
Indicates that one entity has a formal or recognized charitable affiliation or partnership with another entity.
- 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_69b3454f739481909ff6c28331f0c0b9 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b352843d7c8190929b94c94eaa63df |
completed | March 12, 2026, 11:55 p.m. |
| PD | Predicate disambiguation | batch_69b34f572efc8190bad1e5078cbcb75a |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b3501834448190bedf775a80da4778 |
completed | March 12, 2026, 11:45 p.m. |
Created at: March 12, 2026, 11:19 p.m.