Triple
T15803708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glosas Emilianenses |
E383158
|
entity |
| Predicate | hasApproximateNumberOfGlosses |
P120143
|
FINISHED |
| Object | over 1000 |
—
|
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: over 1000 | Statement: [Glosas Emilianenses, hasApproximateNumberOfGlosses, over 1000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateNumberOfGlosses Context triple: [Glosas Emilianenses, hasApproximateNumberOfGlosses, over 1000]
-
A.
hasMultilingualGlosses
Indicates that an entity is associated with glosses or explanatory labels available in multiple languages.
-
B.
hasGlossesBy
Indicates a relationship where one entity provides or is associated with explanatory glosses or definitions for another entity.
-
C.
hasGlossonym
Indicates a relationship where an entity is associated with the specific name or term used to refer to a language (its glossonym).
-
D.
hasEnglishGloss
Indicates that one entity serves as the English-language gloss or explanatory translation for the other entity.
-
E.
hasApproximateNumberOfLanguages
Indicates that an entity is associated with a quantity representing an estimated or non-exact count of languages.
- 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_69d86da2858c819090cc8481e7207b6e |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b524835c8190ae286b2562f07756 |
completed | April 16, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69e0053b847c8190945726c3ddac21cc |
completed | April 15, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69e00e48d49c819081afccb02f9cf18b |
completed | April 15, 2026, 10:16 p.m. |
Created at: April 10, 2026, 4:48 a.m.