Triple
T8789757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soroca |
E209131
|
entity |
| Predicate | fortressRebuiltInStoneInCentury |
P11509
|
FINISHED |
| Object | 16th century |
—
|
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: 16th century | Statement: [Soroca, fortressRebuiltInStoneInCentury, 16th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fortressRebuiltInStoneInCentury Context triple: [Soroca, fortressRebuiltInStoneInCentury, 16th century]
-
A.
fortressWallBuiltInCentury
Indicates that a fortress wall was constructed during a specified century.
-
B.
rebuiltInStone
Indicates that a previously existing structure was reconstructed using stone as the primary building material.
-
C.
fortressBuiltUnder
Indicates that one structure or location was constructed directly beneath or within the protective area of a fortress.
-
D.
castleBuilt
Indicates that a castle has been constructed or established, typically by a specific agent or during a particular time period.
-
E.
rebuiltInCentury
chosen
Indicates that an existing structure or entity was reconstructed or significantly rebuilt during a specified century.
- 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_69ca836168108190bb43d3dc235c1f55 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5f8b0c108190af53d4bb9b132c5c |
completed | March 31, 2026, 11:58 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1d48f08190b325a77d4c76d223 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:43 p.m.