Triple
T3361583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Tyler |
E70732
|
entity |
| Predicate | guardedAsset |
P26862
|
FINISHED |
| Object | privacy of lodge proceedings |
—
|
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: privacy of lodge proceedings | Statement: [Grand Tyler, guardedAsset, privacy of lodge proceedings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: guardedAsset Context triple: [Grand Tyler, guardedAsset, privacy of lodge proceedings]
-
A.
protectedAsset
chosen
Indicates that one entity serves as a safeguarded or defended resource in relation to another entity.
-
B.
protectedAs
Indicates that one entity is safeguarded, preserved, or kept safe by another entity or under a specified protective status or mechanism.
-
C.
protectedAspect
Indicates that one entity is safeguarded, preserved, or kept safe by another entity or mechanism.
-
D.
protectedFrom
Indicates that one entity is shielded or safeguarded against harm, damage, or adverse effects caused by another entity or factor.
-
E.
guardedSectionOf
Indicates a relationship where one entity serves as a protective or security boundary for a specific section or portion of another entity.
- 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_69ad85a660c48190998489309a3b4869 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb26906948190851a7b7d543a4d64 |
completed | March 8, 2026, 5:31 p.m. |
| PD | Predicate disambiguation | batch_69ada4317e288190ab7d0f66e9dba65f |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:13 p.m.