Triple
T27547421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bijrani zone |
E695399
|
entity |
| Predicate | hasEntryGate |
P4365
|
FINISHED |
| Object | Amdanda Gate |
—
|
NE NERFINISHED |
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: Amdanda Gate | Statement: [Bijrani zone, hasEntryGate, Amdanda Gate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEntryGate Context triple: [Bijrani zone, hasEntryGate, Amdanda Gate]
-
A.
hasGate
chosen
Indicates that one entity possesses, includes, or is equipped with a gate as part of its structure or configuration.
-
B.
hasGatesFor
Indicates that one entity is equipped with or provides access through one or more gates intended for another entity.
-
C.
hasEntryOn
Indicates that one entity contains or includes an entry, record, or listing about another entity.
-
D.
hasGatekeeper
Indicates that one entity serves as a controlling or mediating gatekeeper for access to another entity.
-
E.
hasEntranceControl
Indicates that an entity implements or is subject to mechanisms that regulate or control access to its entrance.
- 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_69ef5386c3e08190bfe33aa326e1f72b |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f6aaf50be08190a2b62a6d881f8aee |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1c555081908787dbf76147f180 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 27, 2026, 1:33 p.m.