Triple
T27843629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Плоштад Македонија |
E703754
|
entity |
| Predicate | еРеконструиранВоРамкиНа |
P12646
|
FINISHED |
| Object | проектот Скопје 2014 |
—
|
NE NERFINISHED |
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: проектот Скопје 2014 | Statement: [Плоштад Македонија, еРеконструиранВоРамкиНа, проектот Скопје 2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: еРеконструиранВоРамкиНа Context triple: [Плоштад Македонија, еРеконструиранВоРамкиНа, проектот Скопје 2014]
-
A.
reconstructedIn
chosen
Indicates that something has been rebuilt, restored, or re-created within a particular context, location, or medium.
-
B.
reconstructs
Indicates performing an action to rebuild, restore, or reassemble something from its parts, damage, or prior state.
-
C.
reconstructedAs
Indicates that one entity has been rebuilt, recreated, or inferred based on evidence, models, or partial information from another entity.
-
D.
reconstructedAsPartOf
Indicates that one entity has been rebuilt, restored, or recreated as a component or segment of another, larger whole.
-
E.
reconstructedWith
Indicates that something has been rebuilt, restored, or reassembled using a specified method, material, or set of components.
- 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_69ef840d9e3c819093615ebff4ec22be |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f638d838c481909fbe470bb85c30b1 |
completed | May 2, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69f6318ae6f08190b3f85f9201046a15 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 6:05 p.m.