Triple
T37348394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nǁng language |
E927244
|
entity |
| Predicate | fieldworkPeriod |
P108116
|
FINISHED |
| Object | intensively documented since the 1990s |
—
|
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: intensively documented since the 1990s | Statement: [Nǁng language, fieldworkPeriod, intensively documented since the 1990s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fieldworkPeriod Context triple: [Nǁng language, fieldworkPeriod, intensively documented since the 1990s]
-
A.
periodOfFieldwork
chosen
Indicates the time span during which the fieldwork activity took place.
-
B.
partOfWorkPeriod
Indicates that a specific time span is contained within, and belongs to, a larger defined work period.
-
C.
timePeriodOfWorks
Indicates the span of time during which the associated works were created, produced, or active.
-
D.
locationPeriod
Indicates that an entity is associated with being at a particular location during a specified time period.
-
E.
collaborationPeriod
Indicates the time span during which two or more entities are actively engaged in a collaborative relationship or joint activity.
- 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_69f76eb5e034819088e53ab5b7909a68 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba68077788190b311e027435fcf87 |
completed | May 6, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fba34c65ac8190b298f0f00d1dcc0e |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:16 p.m.