Triple
T32925031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sulṭán |
E842245
|
entity |
| Predicate | hasNumericalValueInYearStructure |
P112288
|
FINISHED |
| Object | 4th month of 19 |
—
|
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: 4th month of 19 | Statement: [Sulṭán, hasNumericalValueInYearStructure, 4th month of 19]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumericalValueInYearStructure Context triple: [Sulṭán, hasNumericalValueInYearStructure, 4th month of 19]
-
A.
hasNumericalValue
Indicates that an entity is associated with a specific numeric quantity or measurement.
-
B.
hasNumberInYear
Indicates that a specific number is associated with or occurs within a given year.
-
C.
hasLetterNumberInYear
Indicates that a specific letter or document is assigned a particular sequential number within a given year.
-
D.
hasYearType
Indicates a relationship where an entity is associated with a specific classification or category of year (such as calendar, fiscal, academic, or other year type).
-
E.
hasNumberInStructure
chosen
Indicates that an entity’s structure includes or contains a specific numerical value or component.
- 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_69f34948adfc8190a937f1f622783c0b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fe349879848190bcd77e3cc3470458 |
completed | May 8, 2026, 7:08 p.m. |
| PD | Predicate disambiguation | batch_69fe31e3cf908190b23ebc2f7fe58722 |
completed | May 8, 2026, 6:56 p.m. |
Created at: May 1, 2026, 1:20 a.m.