Triple
T579757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hungarian language |
E15030
|
entity |
| Predicate | hasOldestRecordsFrom |
P6054
|
FINISHED |
| Object | 10th 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: 10th century | Statement: [Hungarian language, hasOldestRecordsFrom, 10th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOldestRecordsFrom Context triple: [Hungarian language, hasOldestRecordsFrom, 10th century]
-
A.
isOldest
Indicates that one entity has a greater age than all other relevant entities in the comparison set.
-
B.
isOldestOrderOf
Indicates that one order is the earliest or first created among a set of related orders for a given context or entity.
-
C.
historicallyRecordedSince
chosen
Indicates that the existence, occurrence, or recognition of one entity has been documented in historical records starting from the time specified by another entity.
-
D.
hasLongTermDatasetSince
Indicates that an entity has maintained or used a particular dataset continuously starting from a specified point in time.
-
E.
hasMigrationHistoryFrom
Indicates that an entity has a recorded history of migrating or moving from a specified origin location or source.
- 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_69a4935783b8819082b77726ec10cc42 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49b6c358081908f458b9e3e208c0d |
completed | March 1, 2026, 8:02 p.m. |
| PD | Predicate disambiguation | batch_69a494c692288190b88f30299516b5ba |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:33 p.m.