Triple
T30593658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Woccon language |
E778727
|
entity |
| Predicate | primarySourcesLocation |
P203996
|
FINISHED |
| Object | colonial-era English accounts |
—
|
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: colonial-era English accounts | Statement: [Woccon language, primarySourcesLocation, colonial-era English accounts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primarySourcesLocation Context triple: [Woccon language, primarySourcesLocation, colonial-era English accounts]
-
A.
primarySources
Indicates that one entity serves as an original, authoritative source of information or evidence for another entity.
-
B.
primarySourcesDiscussed
Indicates that the primary source materials are examined, analyzed, or discussed in relation to the subject.
-
C.
loreSourceType
Indicates the type or category of source from which a piece of lore or background information is derived.
-
D.
commonSources
Indicates that two or more entities share the same origin, cause, or source.
-
E.
sourceLocatedOn
Indicates that the source entity is physically situated on the surface or area of the target entity.
- F. None of above. chosen
Provenance (4 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_69f224a1570c8190a85d3ac330479a79 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a0308a4591081909018e2ba5d70096e |
completed | May 12, 2026, 11:01 a.m. |
| PD | Predicate disambiguation | batch_6a03079299708190a2ecaf14d3f06f48 |
completed | May 12, 2026, 10:57 a.m. |
| PDg | Predicate description generation | batch_6a0308a3b03c8190b7fc9553afe06cb5 |
completed | May 12, 2026, 11:01 a.m. |
Created at: April 29, 2026, 8:24 p.m.