Triple
T6774971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lemerig |
E155132
|
entity |
| Predicate | numberOfSpeakersDate |
P73202
|
FINISHED |
| Object | early 21st 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: early 21st century | Statement: [Lemerig, numberOfSpeakersDate, early 21st century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfSpeakersDate Context triple: [Lemerig, numberOfSpeakersDate, early 21st century]
-
A.
hasSpeakerType
Indicates that an entity functions in a particular role or category as a speaker (e.g., narrator, character, announcer) within a given context.
-
B.
lastKnownSpeakersDate
Indicates the date on which the last known speakers of a language or dialect were recorded or documented.
-
C.
hasSpeakersIn
Indicates that an entity (such as an event, conference, or session) includes or is associated with speakers located in or belonging to a specified place or group.
-
D.
haveSpeakerPopulation
Indicates that an entity has a specified number or population size of people who speak a particular language.
-
E.
hasApproximateTotalSpeakers
Indicates that an entity is associated with an estimated or roughly calculated number of total speakers, rather than an exact count.
- 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_69c68812ef7c819099369f51febb725c |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d24ddaf08190baffbff991eeb458 |
completed | March 27, 2026, 6:54 p.m. |
| PD | Predicate disambiguation | batch_69c6d094105881909c5806eb4afa6306 |
completed | March 27, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69c6d1d5f1908190989efc8a2d18c965 |
completed | March 27, 2026, 6:52 p.m. |
Created at: March 27, 2026, 2:13 p.m.