Triple
T33921776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Woodland Trust |
E869634
|
entity |
| Predicate | charityNumberScotland |
P22705
|
FINISHED |
| Object | SC038885 |
—
|
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: SC038885 | Statement: [Woodland Trust, charityNumberScotland, SC038885]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: charityNumberScotland Context triple: [Woodland Trust, charityNumberScotland, SC038885]
-
A.
charityNumber
chosen
Indicates that an entity is associated with a specific registered charity identification number.
-
B.
charitySingle
Indicates that an entity makes a one-time charitable contribution or donation to another entity.
-
C.
charityModel
Indicates a relationship where an entity operates according to, or is characterized by, a particular model or framework for conducting charitable activities or philanthropy.
-
D.
associatedCharity
Indicates that one entity has a formal or recognized charitable affiliation or partnership with another entity.
-
E.
charityComponent
Indicates that one entity functions as a charitable element, feature, or part within another entity or larger arrangement.
- 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_69f349992c508190aa4afa24a086cc8c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7064e906881909c3186c646145d34 |
completed | May 3, 2026, 8:24 a.m. |
| PD | Predicate disambiguation | batch_69f70100ec1c8190a6b97f50e88891f2 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:49 a.m.