Triple
T26198471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Namghars of Assam |
E655168
|
entity |
| Predicate | entryPolicy |
P58
|
FINISHED |
| Object | open to all community members |
—
|
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: open to all community members | Statement: [Namghars of Assam, entryPolicy, open to all community members]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: entryPolicy Context triple: [Namghars of Assam, entryPolicy, open to all community members]
-
A.
boardingPolicy
Indicates the rules or procedures governing how and in what order passengers are allowed to board a vehicle or vessel.
-
B.
admissionPolicy
chosen
Indicates the rules or criteria governing whether and how entities are allowed to be admitted or granted access.
-
C.
locationPolicy
Indicates a rule or constraint governing where an entity is allowed, required, or restricted to be located.
-
D.
establishedPolicy
Indicates that a policy has been formally created, adopted, and put into effect as a guiding rule or standard.
-
E.
entryCondition
Indicates the prerequisite state, criteria, or circumstances that must be satisfied before entering or initiating a particular process, state, or context.
- 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_69ee5b48236c81908fe385b6afc4f60b |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f60cd8c4608190bdf0cc6142264239 |
completed | May 2, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69f5b007ec1c819092e2c3605933f60b |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 26, 2026, 8:47 p.m.