Triple
T4950987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Navreh |
E111166
|
entity |
| Predicate | approxGregorianMonth |
P16936
|
FINISHED |
| Object | March |
—
|
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: March | Statement: [Navreh, approxGregorianMonth, March]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approxGregorianMonth Context triple: [Navreh, approxGregorianMonth, March]
-
A.
correspondsRoughlyToGregorianMonths
chosen
Indicates that one or more time periods or units align approximately, but not exactly, with specific months in the Gregorian calendar.
-
B.
monthNumber
Indicates the numerical position of a month within a calendar year (e.g., January = 1, February = 2, etc.).
-
C.
monthObserved
Indicates the month during which an event, observation, or measurement took place.
-
D.
dateRelativeToGregorian
Indicates how a given date is positioned or expressed in relation to the standard Gregorian calendar date.
-
E.
hasAverageMonthLength
Indicates that an entity is associated with a specified average length of a month, typically expressed in days.
- 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_69bd441721cc819085c7e33fe0876818 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd71b561ec81908083225269222e96 |
completed | March 20, 2026, 4:11 p.m. |
| PD | Predicate disambiguation | batch_69bd6c3aa1388190b3e0c8ee1ba1e4fa |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:31 p.m.