Triple
T16479209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M’Zab Valley |
E400270
|
entity |
| Predicate | numberOfHistoricKsour |
P122937
|
FINISHED |
| Object | 5 |
—
|
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: 5 | Statement: [M’Zab Valley, numberOfHistoricKsour, 5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfHistoricKsour Context triple: [M’Zab Valley, numberOfHistoricKsour, 5]
-
A.
historicalVersion
Indicates that one entity represents an earlier or past version in the history or evolution of another entity.
-
B.
historicalLength
Indicates the duration or extent of time over which something has existed, occurred, or been recorded in the past.
-
C.
estimatedHistory
Indicates that there is an inferred or approximated record of past states, events, or values associated with an entity or relationship.
-
D.
historicallyKeptAt
Indicates that an entity was stored or maintained at a particular location during a past period of time.
-
E.
resourceHistoricallyExtracted
Indicates that a resource was extracted from a location or entity during some period in the past, but not necessarily in the present.
- F. None of above. chosen
Provenance (4 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_69d883813098819084f5409539723b59 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e01230881908b2147a25f78b7f4 |
completed | April 18, 2026, 7:08 a.m. |
| PD | Predicate disambiguation | batch_69e22706b0588190a48a951c5211a617 |
completed | April 17, 2026, 12:26 p.m. |
| PDg | Predicate description generation | batch_69e24556c1348190902a4d116c3137d9 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 10, 2026, 5:13 a.m.