Triple
T3539070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yana language |
E74837
|
entity |
| Predicate | timeDepthOfDocumentation |
P23807
|
FINISHED |
| Object | approximately 1911–1916 |
—
|
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 1911–1916 | Statement: [Yana language, timeDepthOfDocumentation, approximately 1911–1916]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeDepthOfDocumentation Context triple: [Yana language, timeDepthOfDocumentation, approximately 1911–1916]
-
A.
hasTimeDepth
Indicates that something possesses or spans a measurable extent of time, such as duration, historical depth, or temporal layering.
-
B.
documentationLevel
Indicates the extent or thoroughness to which something is described, specified, or supported by written or recorded documentation.
-
C.
documentationPeriod
chosen
Indicates the time span or interval during which something is documented, recorded, or valid in the documentation.
-
D.
testDepth
Indicates that an entity is evaluated or measured based on how deep or thorough it is, often in terms of levels, layers, or extent below a surface or baseline.
-
E.
documentedUsing
Indicates that something is recorded, described, or specified by means of a particular document, tool, or documentation method.
- 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_69ad85d274cc8190ab59c97298a1cfbf |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbcca5e008190abcfe40c8902a95f |
completed | March 8, 2026, 6:15 p.m. |
| PD | Predicate disambiguation | batch_69adae15749881909b847c6ca73c934e |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:20 p.m.