Triple
T28287459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andrusovo |
E713322
|
entity |
| Predicate | eventCenturyAtLocation |
P10925
|
FINISHED |
| Object | 17th 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: 17th century | Statement: [Andrusovo, eventCenturyAtLocation, 17th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eventCenturyAtLocation Context triple: [Andrusovo, eventCenturyAtLocation, 17th century]
-
A.
timeLocatedInCentury
chosen
Indicates that an event or temporal entity occurs within, or is situated in, a specific century.
-
B.
latestCentury
Indicates that the associated time or event occurs in, or belongs to, the most recent century relative to a given reference point.
-
C.
encounterCentury
Indicates that an entity has an encounter or interaction that occurs within a specified century.
-
D.
centuryCelebrated
Indicates that a particular century is being honored, commemorated, or formally celebrated in some way.
-
E.
emergedByCentury
Indicates that something came into existence, became prominent, or first appeared 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_69efb52371d88190a1381c4e58a3b731 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f65a6c900881908f18b61273d7bf8d |
completed | May 2, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69f659ce58408190ba9e007b4810d4d0 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 27, 2026, 11:27 p.m.