Triple
T25328906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Negus |
E635095
|
entity |
| Predicate | equivalentEnglishGloss |
P31361
|
FINISHED |
| Object | ruler |
—
|
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: ruler | Statement: [Negus, equivalentEnglishGloss, ruler]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: equivalentEnglishGloss Context triple: [Negus, equivalentEnglishGloss, ruler]
-
A.
hasEnglishGloss
Indicates that one entity serves as the English-language gloss or explanatory translation for the other entity.
-
B.
meaningGloss
Indicates that the predicate provides a brief explanatory phrase or paraphrase capturing the meaning or sense of another expression or item.
-
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.
languageEquivalent
Indicates that two linguistic expressions convey the same meaning or function across different languages or language varieties.
-
E.
EnglishTranslation
chosen
Indicates that one expression is the English-language translation equivalent of another expression.
- 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_69e75a9908108190a95427a97020632a |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f55e519978819087a1676564a74630 |
completed | May 2, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69f4a0edd10c81908a052ab864d57c54 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 21, 2026, 1:30 p.m.