Triple
T2759105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Massachusett language |
E61176
|
entity |
| Predicate | earlyDocumentation |
P12788
|
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: [Massachusett language, earlyDocumentation, 17th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earlyDocumentation Context triple: [Massachusett language, earlyDocumentation, 17th century]
-
A.
documentedUsing
Indicates that something is recorded, described, or specified by means of a particular document, tool, or documentation method.
-
B.
legacyDocumentedBy
chosen
Indicates that information about a legacy item or concept is recorded or described in a specific documenting source.
-
C.
earlyTraining
Indicates that an entity receives or provides training at an early stage relative to a process, development period, or typical timeline.
-
D.
earlyActivity
Indicates that an entity begins or performs a specified activity earlier than a usual, expected, or referenced time.
-
E.
earlyRoute
Indicates that a route or path is taken or scheduled earlier than a standard, expected, or alternative route.
- 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_69ab4b7a85bc819094a349b84beb1f2c |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdb8d34f88190a760111fe303cf24 |
completed | March 7, 2026, 8:02 a.m. |
| PD | Predicate disambiguation | batch_69abd82de7f48190acd614f28644c6da |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:57 p.m.