Triple
T29840169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soroca Fortress |
E757767
|
entity |
| Predicate | hasDefensiveWalls |
P22477
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Soroca Fortress, hasDefensiveWalls, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDefensiveWalls Context triple: [Soroca Fortress, hasDefensiveWalls, yes]
-
A.
hasFortifications
chosen
Indicates that one entity possesses or is equipped with defensive structures or fortification works associated with it.
-
B.
fortressDefended
Indicates that a fortress is actively protected against threats or attacks by some defending force.
-
C.
hasFortificationsFrom
Indicates that an entity possesses or is protected by fortifications that originate from or were constructed by another specified source or period.
-
D.
hasCityWallsFrom
Indicates that a city’s defensive walls originate from, or were constructed starting at, a specified source location or structure.
-
E.
hasCityWallFunction
Indicates that an entity serves the functional role of a city wall, such as providing defense, enclosure, or boundary protection for an urban area.
- 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_69f224593f6c81908785a560fe659f58 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fd6dbd1b648190b1a0b391c03aebc5 |
completed | May 8, 2026, 4:59 a.m. |
| PD | Predicate disambiguation | batch_69fd6a9020548190bbfa845360ac85fb |
completed | May 8, 2026, 4:46 a.m. |
Created at: April 29, 2026, 5:39 p.m.