Triple
T546895
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Lodge |
E12751
|
entity |
| Predicate | canRevoke |
P12751
|
FINISHED |
| Object | lodge charters |
—
|
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: lodge charters | Statement: [Grand Lodge, canRevoke, lodge charters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canRevoke Context triple: [Grand Lodge, canRevoke, lodge charters]
-
A.
canBeRevoked
chosen
Indicates that a previously granted status, permission, or agreement is subject to being withdrawn or canceled.
-
B.
canResign
Indicates that an entity has the authority or option to voluntarily leave a position, role, or membership.
-
C.
canReview
Indicates that one entity has the permission or ability to evaluate, assess, or provide feedback on another entity.
-
D.
canEnforce
Indicates that one entity has the authority or capability to compel compliance with rules, decisions, or obligations upon another entity.
-
E.
canAuthorize
Indicates that one entity has the power or permission to grant approval or official permission for another entity to perform an action or access a resource.
- 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.