Triple
T3557886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince Hall Freemasonry |
E75263
|
entity |
| Predicate | hasMasonicBodyType |
P50336
|
FINISHED |
| Object | Grand Lodge system |
—
|
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: Grand Lodge system | Statement: [Prince Hall Freemasonry, hasMasonicBodyType, Grand Lodge system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMasonicBodyType Context triple: [Prince Hall Freemasonry, hasMasonicBodyType, Grand Lodge system]
-
A.
hasStudentBodyType
Indicates that an educational institution possesses a student body characterized by a particular type or classification.
-
B.
residesOverBodyType
Indicates that one entity is positioned or located above another entity that is characterized by a specific body type.
-
C.
religiousBodyType
Indicates the type or classification of a religious organization or body to which an entity is related.
-
D.
hasBodyPlanFeature
Indicates that an organism’s body plan includes a specific structural or morphological feature.
-
E.
hasInspectionBody
Indicates that an entity is associated with or overseen by a specific organization responsible for inspecting or auditing it.
- 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_69ad85d45090819086f34fb85d850a1e |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc086e6688190b90ae356e18b953e |
completed | March 8, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69adb834779081908468e182d5f6cf02 |
completed | March 8, 2026, 5:56 p.m. |
| PDg | Predicate description generation | batch_69adb9bbb62c8190989629ca11733e1b |
completed | March 8, 2026, 6:02 p.m. |
Created at: March 8, 2026, 3:20 p.m.