Triple
T25502757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Religious Liberty Award |
E639161
|
entity |
| Predicate | sponsorIdeology |
P158604
|
FINISHED |
| Object | humanist |
—
|
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: humanist | Statement: [Religious Liberty Award, sponsorIdeology, humanist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sponsorIdeology Context triple: [Religious Liberty Award, sponsorIdeology, humanist]
-
A.
sponsorTo
Indicates that one entity provides support, funding, or endorsement to another entity, typically to enable or promote the latter’s activities or initiatives.
-
B.
sponsorInHouse
Indicates that one entity formally supports, promotes, or funds another entity within the same organization, institution, or internal setting.
-
C.
sponsorFrom
Indicates that one entity provides sponsorship or financial backing originating from a specified source entity.
-
D.
supportedCampaignOf
Indicates that one entity actively backed, promoted, or provided assistance to the campaign associated with another entity.
-
E.
sponsorAcronym
Indicates that one entity is the acronym or abbreviated form used to refer to the sponsoring organization of 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_69e75dbd09308190b6b5f0afdc12ec6d |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f80381a481909f39b55b220ad261 |
completed | May 2, 2026, 1:11 p.m. |
| PD | Predicate disambiguation | batch_69f468421ba08190880eac99135e5970 |
completed | May 1, 2026, 8:45 a.m. |
| PDg | Predicate description generation | batch_69f46d361c348190b5fdfd805ecde01b |
completed | May 1, 2026, 9:07 a.m. |
Created at: April 21, 2026, 2:45 p.m.