Triple
T13755683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Foreign Relations of the United States series |
E330468
|
entity |
| Predicate | hasOnlineAccessPoint |
P108407
|
FINISHED |
| Object | history.state.gov |
—
|
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: history.state.gov | Statement: [Foreign Relations of the United States series, hasOnlineAccessPoint, history.state.gov]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOnlineAccessPoint Context triple: [Foreign Relations of the United States series, hasOnlineAccessPoint, history.state.gov]
-
A.
hasAccessPointFrom
Indicates that an entity can be reached or entered from a specific access point.
-
B.
hasOnlineProvision
Indicates that an entity offers or supports a service, feature, or function through an online or internet-based channel.
-
C.
isAvailableOnline
chosen
Indicates that something can be accessed or obtained via the internet.
-
D.
isOnLine
Indicates that one entity is located directly along, or in contact with, a specified line or linear path.
-
E.
hasNearbyAccess
Indicates that one entity has convenient, close-proximity access to another resource, service, or location.
- 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_69d81c573f288190aa2403d484fa3d49 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02179c948190a652cc8c586e418f |
completed | April 14, 2026, 9 a.m. |
| PD | Predicate disambiguation | batch_69dbbe97846c819093b00ea117b64e0d |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 10:09 p.m.