Triple
T35974354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Atlantic Norse world |
E1040370
|
entity |
| Predicate | explorationFrontier |
P184299
|
FINISHED |
| Object | North America |
E335
|
NE 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: North America | Statement: [North Atlantic Norse world, explorationFrontier, North America]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: explorationFrontier Context triple: [North Atlantic Norse world, explorationFrontier, North America]
-
A.
explorationType
Indicates the specific kind or category of exploration activity associated with an entity or event.
-
B.
frontierSystem
Indicates a system that lies at or near the boundary or edge of a defined region, domain, or area of control.
-
C.
earlyExplorer
Indicates that an entity explored or investigated a place, field, or subject significantly earlier than most others.
-
D.
explores
Indicates actively investigating, traveling through, or examining something in order to discover or learn more about it.
-
E.
potentialForHumanExploration
Indicates the extent to which a location, object, or environment is suitable or promising for future human exploration activities.
- F. None of above. chosen
Provenance (5 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_69f76e27758c81909b711cf38a130aaf |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7ad15f3b88190b7c9742a734fec5f |
completed | May 3, 2026, 8:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38b6fdd01481909a20d247c5ba542a |
completed | June 22, 2026, 4:15 a.m. |
| PD | Predicate disambiguation | batch_69f7ab75387c819091afc3c2128eb903 |
completed | May 3, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69f7acad20388190b9b10270ca9bdfbc |
completed | May 3, 2026, 8:14 p.m. |
Created at: May 3, 2026, 4:07 p.m.