Triple
T14226831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abhinav Bharat Society |
E352641
|
entity |
| Predicate | secretCode |
P26712
|
FINISHED |
| Object | oath-bound membership |
—
|
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: oath-bound membership | Statement: [Abhinav Bharat Society, secretCode, oath-bound membership]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secretCode Context triple: [Abhinav Bharat Society, secretCode, oath-bound membership]
-
A.
securityCodename
Indicates that an entity is assigned a specific codename used for security, confidentiality, or protective identification purposes.
-
B.
missionCode
Indicates a code or identifier assigned to a specific mission that links entities to that mission.
-
C.
coDecipherer
Indicates that two or more entities jointly participated in deciphering or decoding something together.
-
D.
seaCode
Indicates a standardized code or identifier assigned to a sea or maritime area.
-
E.
codeword
chosen
Indicates that one entity serves as a codeword or encoded representation used to convey, reference, or stand in for another entity within a coding or communication system.
- 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_69d8278a06e481908b5d6af0a8afe737 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de6228e53c8190abbe4e2d88a7362a |
completed | April 14, 2026, 3:50 p.m. |
| PD | Predicate disambiguation | batch_69de05bf069c8190b69f00f00f5eb126 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1:07 a.m.