Triple
T19638627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shuvalov Palace |
E471467
|
entity |
| Predicate | functionHistorical |
P2715
|
FINISHED |
| Object | noble family residence |
—
|
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: noble family residence | Statement: [Shuvalov Palace, functionHistorical, noble family residence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: functionHistorical Context triple: [Shuvalov Palace, functionHistorical, noble family residence]
-
A.
historicalFunction
chosen
Indicates the role, purpose, or activity an entity had during a past period or in a historical context.
-
B.
historicalRecord
Indicates that there exists a documented account or record capturing information about an entity, event, or relationship from the past.
-
C.
estimatedHistory
Indicates that there is an inferred or approximated record of past states, events, or values associated with an entity or relationship.
-
D.
historicalValue
Indicates that something possesses significance, importance, or relevance due to its connection with past events, periods, or developments.
-
E.
hasHistoricalData
Indicates that an entity possesses recorded information or records about past events, states, or values relevant to it.
- 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_69d8e511f28481909f4bc3ea9191e54a |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e641090c408190b2adb8a6abf1b4c9 |
completed | April 20, 2026, 3:06 p.m. |
| PD | Predicate disambiguation | batch_69e514e5cb108190ae260e466c447314 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:44 p.m.