Triple
T31395879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Code of Handsome Lake |
E800861
|
entity |
| Predicate | laterDocumentedBy |
P4310
|
FINISHED |
| Object | anthropologists |
—
|
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: anthropologists | Statement: [Code of Handsome Lake, laterDocumentedBy, anthropologists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterDocumentedBy Context triple: [Code of Handsome Lake, laterDocumentedBy, anthropologists]
-
A.
legacyDocumentedBy
Indicates that information about a legacy item or concept is recorded or described in a specific documenting source.
-
B.
laterUsedBy
Indicates that something is subsequently utilized or employed by a specified entity at a later time.
-
C.
documentedBy
chosen
Indicates that something is recorded, described, or evidenced in a specific document or set of documents.
-
D.
laterVersion
Indicates that one entity is a subsequent or more recent version of another entity in a version sequence.
-
E.
laterAccessedBy
Indicates that an entity is subsequently accessed or used by another entity at a later point in time.
- 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_69f224ea9998819086ae2e4f4f4091c8 |
completed | April 29, 2026, 3:34 p.m. |
| NER | Named-entity recognition | batch_69ff3fb2318c81908a46c2f513608935 |
completed | May 9, 2026, 2:07 p.m. |
| PD | Predicate disambiguation | batch_69ff3e96dcc48190819f6204680d84aa |
completed | May 9, 2026, 2:03 p.m. |
Created at: April 29, 2026, 9:19 p.m.