Triple
T546893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Lodge |
E12751
|
entity |
| Predicate | canWithholdRecognitionFrom |
P9387
|
FINISHED |
| Object | irregular Grand Lodges |
—
|
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: irregular Grand Lodges | Statement: [Grand Lodge, canWithholdRecognitionFrom, irregular Grand Lodges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canWithholdRecognitionFrom Context triple: [Grand Lodge, canWithholdRecognitionFrom, irregular Grand Lodges]
-
A.
isWithheldBy
chosen
Indicates that something (such as information, resources, or permission) is deliberately not given, released, or made available by a particular entity.
-
B.
cannotReview
Indicates that an entity is not permitted or able to perform a review of another entity or item.
-
C.
canBeRevoked
Indicates that a previously granted status, permission, or agreement is subject to being withdrawn or canceled.
-
D.
canAward
Indicates that one entity has the authority or ability to grant an award, honor, or recognition to another entity.
-
E.
canRejectBills
Indicates the authority or power an entity has to refuse approval of proposed bills or legislative measures.
- 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_69a49334226c81908b0ea1689ef6aa3f |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a498e150e88190b35b1bc7a376ca07 |
completed | March 1, 2026, 7:52 p.m. |
| PD | Predicate disambiguation | batch_69a494b957988190bc269e372df2f0b2 |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:32 p.m.