Triple
T30284395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zamoyski family |
E770190
|
entity |
| Predicate | continuedAfterPartition |
P95922
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Zamoyski family, continuedAfterPartition, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: continuedAfterPartition Context triple: [Zamoyski family, continuedAfterPartition, yes]
-
A.
continuedThrough
chosen
Indicates that an event, state, or process persisted without interruption across or beyond a specified point, period, or boundary.
-
B.
partOfAfter
Indicates that one entity becomes a component or subset of another entity at some point after a specified time or event.
-
C.
continuedBy
Indicates that one entity carries on, extends, or resumes the activity, process, or sequence initiated by another entity.
-
D.
continuesInto
Indicates that one entity extends forward in time, space, or sequence so that it directly proceeds into and forms a continuous progression with another entity.
-
E.
continuedInRegion
Indicates that an event, process, or state persisted or carried on within a specified geographic or spatial region.
- 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_69f224868fa8819099127eaf8855a28f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7764ab1fc81909f9348db87bd7692 |
completed | May 3, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69f76905d9c88190b1ee810bc9ab644f |
completed | May 3, 2026, 3:25 p.m. |
Created at: April 29, 2026, 7:45 p.m.