Triple
T9252049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kitay-gorod |
E222347
|
entity |
| Predicate | hasCityGateRemains |
P87789
|
FINISHED |
| Object | Kitay-gorod wall fragments |
—
|
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: Kitay-gorod wall fragments | Statement: [Kitay-gorod, hasCityGateRemains, Kitay-gorod wall fragments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCityGateRemains Context triple: [Kitay-gorod, hasCityGateRemains, Kitay-gorod wall fragments]
-
A.
hasCityGateFunction
Indicates that something serves the role or function of a city gate, such as controlling access, passage, or boundary between a city and its surroundings.
-
B.
hasCityGateStatus
Indicates the status or condition of a city gate in relation to a given entity.
-
C.
oneOfFewRemainingGatesOf
Indicates that the subject is one of the small number of remaining gates belonging to or associated with the object.
-
D.
hasGate
Indicates that one entity possesses, includes, or is equipped with a gate as part of its structure or configuration.
-
E.
hasNearbyGate
Indicates that one entity has a gate located in close physical proximity to it.
- F. None of above. chosen
Provenance (4 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_69ca841d2b18819089f9faf5b2c2aec0 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd05fb1454819098f452846ca4ca61 |
completed | April 1, 2026, 11:48 a.m. |
| PD | Predicate disambiguation | batch_69cc7a4e79e48190b3200247f4624867 |
completed | April 1, 2026, 1:52 a.m. |
| PDg | Predicate description generation | batch_69cc95597be081908ece2491dd2f0f74 |
completed | April 1, 2026, 3:47 a.m. |
Created at: March 30, 2026, 7:31 p.m.