Triple
T25122925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prowent |
E629313
|
entity |
| Predicate | locatedInTimeSpecific |
P22881
|
FINISHED |
| Object | Second Polish Republic |
E1504
|
NE 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: Second Polish Republic | Statement: [Prowent, locatedInTimeSpecific, Second Polish Republic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInTimeSpecific Context triple: [Prowent, locatedInTimeSpecific, Second Polish Republic]
-
A.
locatedAtTime
Indicates that a location relationship holds during a specific time or time interval.
-
B.
locatedInTimeBefore
Indicates that one temporal event or interval occurs entirely before another in time.
-
C.
locatedInTimeZone
Indicates that an entity exists or an event occurs within the temporal bounds defined by a specific time zone.
-
D.
timeLocatedIn
Indicates that an event, state, or entity occurs, exists, or is valid within a specified time or temporal interval.
-
E.
hasTemporalLocation
chosen
Indicates that something occurs, exists, or is valid during a specific time or time interval.
- F. None of above.
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_69e2ff3288048190bd82c3b7f7bd0e62 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a105ce77d348190b7772e56a09d8836 |
completed | May 22, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_69f68b78f29481908cc8f390496dee97 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 18, 2026, 6:28 a.m.