Triple
T7706216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Proto-Ugric language |
E174622
|
entity |
| Predicate | lexicallyContinuedIn |
P61223
|
FINISHED |
| Object | basic vocabulary of Hungarian |
—
|
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: basic vocabulary of Hungarian | Statement: [Proto-Ugric language, lexicallyContinuedIn, basic vocabulary of Hungarian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lexicallyContinuedIn Context triple: [Proto-Ugric language, lexicallyContinuedIn, basic vocabulary of Hungarian]
-
A.
continuedBy
Indicates that one entity carries on, extends, or resumes the activity, process, or sequence initiated by another entity.
-
B.
belongsToContinuity
Indicates that something is part of, or exists within, a specific narrative or temporal continuity.
-
C.
successorInText
Indicates that one text element directly follows another in the sequential order of a text.
-
D.
continuesToward
Indicates that an entity maintains its movement or progression in the direction of a specified target or destination.
-
E.
hasContinuation
chosen
Indicates that one entity serves as a continuation or subsequent part of another entity in a sequence or process.
- 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_69c6995b3e8c8190833108f883d5f53c |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c70402169481909b219dc5f4a64b9b |
completed | March 27, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69c70165e78c8190bf6b3c34e243cb81 |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:03 p.m.