Triple
T29791972
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern Lights |
E756432
|
entity |
| Predicate | charitySingle |
P167880
|
FINISHED |
| Object | Tears Are Not Enough |
—
|
NE NERFINISHED |
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: Tears Are Not Enough | Statement: [Northern Lights, charitySingle, Tears Are Not Enough]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: charitySingle Context triple: [Northern Lights, charitySingle, Tears Are Not Enough]
-
A.
charitySinglePurpose
Indicates that a charity is established and operated for a single, specific charitable purpose rather than multiple distinct purposes.
-
B.
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.
-
C.
charityComponent
Indicates that one entity functions as a charitable element, feature, or part within another entity or larger arrangement.
-
D.
hasCharitySingle
Indicates that an entity is associated with exactly one specific charitable organization or charitable initiative.
-
E.
charityCategory
Indicates the specific type or classification of charitable activity or purpose associated with an 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_69f22454583081908927516cb9938d1d |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f674e2ada081908511761af8eaa114 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f66ac1a4fc81909740d2e52fbe6970 |
completed | May 2, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69f66c59de9881909ebbb7b0ae7ab495 |
completed | May 2, 2026, 9:27 p.m. |
Created at: April 29, 2026, 5:13 p.m.