Triple
T35133507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Etchemin language |
E1014504
|
entity |
| Predicate | timeDepthOfRecords |
P6054
|
FINISHED |
| Object | 17th century |
—
|
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: 17th century | Statement: [Etchemin language, timeDepthOfRecords, 17th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeDepthOfRecords Context triple: [Etchemin language, timeDepthOfRecords, 17th century]
-
A.
depthRecordHeldUntilYear
Indicates the year up to which a particular depth-related record remained valid or unbroken.
-
B.
hasTimeDepth
Indicates that something possesses or spans a measurable extent of time, such as duration, historical depth, or temporal layering.
-
C.
historicallyRecordedSince
chosen
Indicates that the existence, occurrence, or recognition of one entity has been documented in historical records starting from the time specified by another entity.
-
D.
collectionTimespan
Indicates the time period over which a collection exists, is accumulated, or is considered valid.
-
E.
timeIndexed
Indicates that the relationship or property it connects is associated with, or valid during, a specific time or time interval.
- 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_69f76dd9c1848190af70d4882a2c1ad7 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78c6c9bac819083af967f6f403ca7 |
completed | May 3, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69f78b9106008190930b3b3675b737d6 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:02 p.m.