Triple
T30868749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raḥmat |
E786276
|
entity |
| Predicate | hasNumberOfWeeks |
P153182
|
FINISHED |
| Object | approximately 2.7 weeks |
—
|
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: approximately 2.7 weeks | Statement: [Raḥmat, hasNumberOfWeeks, approximately 2.7 weeks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumberOfWeeks Context triple: [Raḥmat, hasNumberOfWeeks, approximately 2.7 weeks]
-
A.
durationInWeeks
chosen
Indicates the length of time associated with something, measured in weeks.
-
B.
hasWeekLength
Indicates the duration of a week associated with an entity, typically expressed as a number of days.
-
C.
hasNumberOfWeekSystems
Indicates the relationship that specifies how many distinct week-based systems are associated with or used by a given entity.
-
D.
signalDuration_weeks
Indicates the length of time, measured in weeks, that a signal persists or is in effect.
-
E.
hasWeekSystem
Indicates that one entity uses, follows, or is organized according to a particular system for dividing time into weeks.
- 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_69f224b9df2c819086f55f8bcf7f382e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd6dbd1b648190b1a0b391c03aebc5 |
completed | May 8, 2026, 4:59 a.m. |
| PD | Predicate disambiguation | batch_69fd6a9020548190bbfa845360ac85fb |
completed | May 8, 2026, 4:46 a.m. |
Created at: April 29, 2026, 8:47 p.m.