Triple
T15305761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Symbolic Lodge |
E365892
|
entity |
| Predicate | maySponsor |
P78082
|
FINISHED |
| Object | Masonic youth organizations |
—
|
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: Masonic youth organizations | Statement: [Symbolic Lodge, maySponsor, Masonic youth organizations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maySponsor Context triple: [Symbolic Lodge, maySponsor, Masonic youth organizations]
-
A.
hasSponsor
Indicates that one entity financially or otherwise supports another entity, typically in exchange for recognition or other benefits.
-
B.
coSponsor
Indicates that an entity jointly supports, endorses, or backs an initiative, proposal, or activity together with one or more others.
-
C.
sponsorTo
chosen
Indicates that one entity provides support, funding, or endorsement to another entity, typically to enable or promote the latter’s activities or initiatives.
-
D.
mayHost
Indicates that an entity is permitted or able to serve as the location or organizer for another entity or event.
-
E.
sponsorInHouse
Indicates that one entity formally supports, promotes, or funds another entity within the same organization, institution, or internal setting.
- 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_69d85a113ee881908e297a1d38dd79fa |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03ccef14c819099c5ebe962e7f867 |
completed | April 16, 2026, 1:35 a.m. |
| PD | Predicate disambiguation | batch_69deca935e2c8190b640987ddfc542b9 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:16 a.m.