Triple
T30804427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lyck |
E784458
|
entity |
| Predicate | historicalNameScript |
P198993
|
FINISHED |
| Object | Latin alphabet |
—
|
NE NERFINISHED |
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: Latin alphabet | Statement: [Lyck, historicalNameScript, Latin alphabet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalNameScript Context triple: [Lyck, historicalNameScript, Latin alphabet]
-
A.
nativeNameScript
Indicates the writing system or script in which an entity’s native name is expressed.
-
B.
historicalNameType
Indicates that the relationship specifies the type or category of a historical name associated with an entity.
-
C.
historicalNameGivenBy
Indicates that one entity is the name historically assigned to another entity by a specific source, culture, or period.
-
D.
languageOfHistoricName
Indicates the language in which a historic or former name of an entity is expressed.
-
E.
historicalNameInLatin
Indicates that an entity has a historically used name expressed in Latin.
- F. None of above. chosen
Provenance (4 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_69f224b3a7ec819096939414d103e31e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ff1a972bf08190860696ffcd887c0f |
completed | May 9, 2026, 11:29 a.m. |
| PD | Predicate disambiguation | batch_69ff184005d88190bf38283ebc499b28 |
completed | May 9, 2026, 11:19 a.m. |
| PDg | Predicate description generation | batch_69ff1a95b6fc81909331bb03e263b5b9 |
completed | May 9, 2026, 11:29 a.m. |
Created at: April 29, 2026, 8:42 p.m.