Triple
T3490639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vitus Bering |
E73720
|
entity |
| Predicate | provedExistenceOf |
P21917
|
FINISHED |
| Object | strait between Asia and North America |
—
|
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: strait between Asia and North America | Statement: [Vitus Bering, provedExistenceOf, strait between Asia and North America]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: provedExistenceOf Context triple: [Vitus Bering, provedExistenceOf, strait between Asia and North America]
-
A.
proved
chosen
Indicates that one entity has demonstrated the truth or validity of another entity (such as a statement, theorem, or claim) through logical or evidential means.
-
B.
proposesExistenceOf
Indicates that one entity puts forward or suggests that another entity should exist or be brought into existence.
-
C.
concludesExistenceOf
Indicates that one entity determines or infers that another entity exists.
-
D.
existedAs
Indicates that one entity had the status, form, or identity of another entity during a certain time or context.
-
E.
existsSince
Indicates that an entity has been in existence or valid from a specified point in time onward.
- 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_69ad85cca8d4819088494e9f3340fab5 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbb94190c8190a81eb41042e51a00 |
completed | March 8, 2026, 6:10 p.m. |
| PD | Predicate disambiguation | batch_69adae0b34908190b2bb5766a2231f7a |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:18 p.m.