Triple
T27421900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jugol |
E693066
|
entity |
| Predicate | hasCityGates |
P21387
|
FINISHED |
| Object | five historic gates |
—
|
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: five historic gates | Statement: [Jugol, hasCityGates, five historic gates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCityGates Context triple: [Jugol, hasCityGates, five historic gates]
-
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.
numberOfGates
chosen
Indicates the quantity of gates associated with or belonging to an entity.
-
C.
hasCityGateRemains
Indicates that a location contains surviving structural remains of a former city gate.
-
D.
hasBoardingGatesFor
Indicates that a location or facility provides designated boarding gates used for embarking passengers onto specific transportation services (such as flights or trains).
-
E.
cityGatesName
Indicates that a set of city gates bears or is identified by a specific name.
- 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_69ef5208617081908f731d312e0fd1bc |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 27, 2026, 12:36 p.m.