Triple
T25415676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Endre |
E636825
|
entity |
| Predicate | usedAsGivenNameInCentury |
P22240
|
FINISHED |
| Object | 20th 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: 20th century | Statement: [Endre, usedAsGivenNameInCentury, 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsGivenNameInCentury Context triple: [Endre, usedAsGivenNameInCentury, 20th century]
-
A.
usedAsFirstNameSinceCentury
chosen
Indicates that an entity has been used as a first name starting from a specified century.
-
B.
isRecordedAsSurnameSinceCentury
Indicates that an entity has been documented or used as a surname starting from a specified century.
-
C.
usedAsFirstNameOf
Indicates that one entity functions as the given or first name of another entity.
-
D.
hasEponymCentury
Indicates that something is named after a person associated with a particular century.
-
E.
usedAsSurname
Indicates that something functions as a family name borne by a person or group of people.
- 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_69e75db4135881909acc287ebcb7a505 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f62d89b89c8190afb372a8172111e7 |
completed | May 2, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69f62c1379f08190836c3e02b0c892df |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 21, 2026, 1:55 p.m.