Triple
T3787750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Armenian Quarter |
E85567
|
entity |
| Predicate | hasNotableGate |
P24982
|
FINISHED |
| Object | Zion Gate vicinity |
—
|
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: Zion Gate vicinity | Statement: [Armenian Quarter, hasNotableGate, Zion Gate vicinity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableGate Context triple: [Armenian Quarter, hasNotableGate, Zion Gate vicinity]
-
A.
notableGate
chosen
Indicates that a gate is recognized as significant, prominent, or noteworthy in some context.
-
B.
hasGate
Indicates that one entity possesses, includes, or is equipped with a gate as part of its structure or configuration.
-
C.
hasNotableFeature
Indicates that an entity possesses a specific characteristic, trait, or attribute that is considered significant or noteworthy.
-
D.
hasNotableHost
Indicates that an entity is associated with a host who is particularly prominent, famous, or otherwise noteworthy.
-
E.
hasNotableIssue
Indicates that an entity is associated with a significant problem, concern, or defect that is noteworthy or exceptional compared to typical cases.
- 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_69aed937fa8881908208ef3801060826 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aee634c6ac819099653c660c286746 |
completed | March 9, 2026, 3:24 p.m. |
| PD | Predicate disambiguation | batch_69aee3d3c92c819081d9d5c45ef37a5d |
completed | March 9, 2026, 3:14 p.m. |
Created at: March 9, 2026, 3:13 p.m.