Triple
T3787549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tashritu |
E85563
|
entity |
| Predicate | correspondsRoughlyTo |
P25442
|
FINISHED |
| Object | September |
—
|
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: September | Statement: [Tashritu, correspondsRoughlyTo, September]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: correspondsRoughlyTo Context triple: [Tashritu, correspondsRoughlyTo, September]
-
A.
partiallyCorrespondsTo
chosen
Indicates that one entity matches or aligns with another entity only in some aspects, segments, or components, rather than fully or exactly.
-
B.
isCloseTo
Indicates that one entity is physically or conceptually near another, within a relatively short distance or range.
-
C.
hasApproximateCoordinates
Indicates that an entity is associated with location coordinates that are estimated or imprecise rather than exact.
-
D.
equivalentTo
Indicates that two entities represent the same concept, value, or state, and can be treated as interchangeable in the given context.
-
E.
coincidesWith
Indicates that two entities occupy the same position, time, or state such that they exactly overlap or occur together.
- 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_69aed937fa8881908208ef3801060826 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aee634c6ac819099653c660c286746 |
completed | March 9, 2026, 3:24 p.m. |
| PD | Predicate disambiguation | batch_69aee3d3c92c819081d9d5c45ef37a5d |
completed | March 9, 2026, 3:14 p.m. |
Created at: March 9, 2026, 3:13 p.m.